mcpbeat Sign in

Verifa MCP Server

by verifa-solutions Your server? Claim it
answering

Verifa is answering right now. Last checked moments ago. 15 installs a week from npm. Last commit 31 Aug 2026.

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

Installs per day peak 11 · avg 3 · -40% w/w
a month agotoday
Uptime history 46 days of history · worst day 89%
46 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
784 ms
Response time
average over 24h
15
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check Verifa every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add verifa --transport http https://api.withverifa.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verifa": {
      "url": "https://api.withverifa.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verifa]
url = "https://api.withverifa.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verifa": {
      "url": "https://api.withverifa.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verifa": {
      "url": "https://api.withverifa.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: VERIFA_API_KEY (Verifa API key (vk_sandbox_... or vk_live_...)), VERIFA_ENV (sandbox or live (inferred from the key if omitted)). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.withverifa.com/mcp streamable-http sign-in 872 ms 0 min ago

Alternatives to Verifa

same job, measured the same way
Stipple — Document Verification & Extraction
by stipple

Document forensics: tamper/AI checks, fields, tables, identity, screening, tenders, citations.

16 tools answering
APICK Identity
by apick

Korean ID document verification and PII masking APIs

16 tools answering
Ardaro Purchase Document Review
by ashevilleislove

Receipt extraction, invoice-to-PO quantity allocation, and free three-document discrepancy checks.

5 tools answering
MCP Jumio
by codespar

MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening

30 installs/wk local only
Axiom Relay
by itr3k

Free agent-service discovery, OpenAPI document checks, and receipt verification. No API key needed.

10 tools answering
MCP Onfido
by codespar

MCP server for Onfido — global identity verification + KYC: applicants, documents, checks, workflows

24 installs/wk local only
Regulations.gov
by 1102tools

Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools.

local only
ConvergeQA Reviews (Critique & Iterate)
by convergeqa

Multi-model Critique and Iterate document reviews with public verification receipts.

98 installs/wk local only

Verifa — questions

Answers built from our own checks of this server.

Why is there no tool list for Verifa?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Verifa working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 784 ms. The bar chart above shows every period we have measured.
How do I connect Verifa?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Verifa?
No API key is involved. Verifa answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Verifa?
It answers our handshake in 784 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Verifa?
The npm package @verifasolutionsinc/mcp-server was installed 15 times in the last week. Week over week that is -40%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Verifa open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.