mcpbeat Sign in

Zyphe MCP Server

answering

Zyphe is answering right now. Last checked 14 min ago.

Run KYB and AML case reviews and configure Zyphe verification flows, forms and API keys.

Uptime history 24 days of history · worst day 99%
24 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
234 ms
Response time
average over 24h
authentication required
Access
streamable-http

Zyphe missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 14 min ago.

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://api.zyphe.com/mcp streamable-http needs auth 238 ms 14 min ago

Alternatives to Zyphe

same job, measured the same way
AI Economics
by piszczek

12 calculators for AI cost, energy and agent verification. Free API, no key.

43 installs/wk local only
Koda
by aabxtract

Verification and memory layer for coding-agent workflows.

48 installs/wk local only
Lumethic Photo Verification
by lumethic

Verify photos are real camera captures, not AI: C2PA and RAW+JPEG forensics. OAuth or API key.

14 tools answering
Tomba MCP Server
by tomba-io

MCP server for Tomba email finder, verification, and contact enrichment API

45 installs/wk 38 tools answering
MCP Aml
by cryptoapis-io

MCP server for AML address verification and transaction screening via Crypto APIs

36 installs/wk local only
GLEIF MCP Server
by olgasafonova

Access the GLEIF LEI database for company verification, KYC, and ownership research.

local only
MCP Verification Gate: conformance and disclosure checker for MCP servers
by ogasurfproject-jpg

Conformance checker for MCP servers. Free, no key, verdicts recomputable and re-measured daily.

5 tools answering
Human For AI
by humanforai

Hire a real human for real-world verification, product testing, AI output review, and errands.

81 installs/wk 6 tools answering

Zyphe — questions

Answers built from our own checks of this server.

Why is there no tool list for Zyphe?
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 Zyphe working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 234 ms. The bar chart above shows every period we have measured.
How do I connect Zyphe?
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 will need your own credentials: it refuses anonymous clients.
Does Zyphe need an API key?
Yes. Every time we knock, Zyphe answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Zyphe?
It answers our handshake in 234 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.