Verifa

io.github.Verifa-Solutions/verifaVersion 0.1.1

Identity verification, document checks, sanctions/PEP screening and case review as agent tools.

Status

Sign-in required780 msNov 14, 2026, 14:43 UTCReachable. It asks for authorization, so we did not look inside.

We could not refresh it, so this page shows the last copy.

Data from the official MCP Registry, checked by run.zero. How we check

Streamable HTTP

https://api.withverifa.com/mcpSign-in required780 msNov 14, 2026, 14:43 UTC

OAuth sign-in

This server asks for sign-in. Your client opens the sign-in when it connects.

claude mcp add --transport http verifa https://api.withverifa.com/mcp

1
2
3

Settings > Connectors > Add custom connector
Name: verifa
Remote MCP server URL: https://api.withverifa.com/mcp

{
  "mcpServers": {
    "verifa": {
      "url": "https://api.withverifa.com/mcp"
    }
  }
}

code --add-mcp '{"name":"verifa","type":"http","url":"https://api.withverifa.com/mcp"}'

Streamable HTTP

npm: @verifasolutionsinc/mcp-server 0.1.0

Package only

claude mcp add verifa -e 'VERIFA_API_KEY=<YOUR_VERIFA_API_KEY>' -- npx -y @verifasolutionsinc/mcp-server@0.1.0

Replace <YOUR_VERIFA_API_KEY> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Tools are visible after sign-in; we do not look inside protected servers.

Registry status: Active
Published: Aug 31, 2026
Updated: Aug 31, 2026
Website: https://withverifa.com/⁠ (opens in a new tab)
Repository: https://github.com/Verifa-Solutions/verifa-mcp-server⁠ (opens in a new tab)
Categories (suggested): SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared