Cyphrex MCP server
Which servers in the official MCP registry are Cyphrex's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-11
- Registry nameio.github.getcyphrex/cyphrex-mcppublished by getcyphrex on GitHub
Published under the GitHub organisation getcyphrex, the same one cyphrex.io links from its homepage. The registry ties that namespace to a GitHub sign-in.
- Stateanswerschecked 2026-10-11
- Tools9
- Server calls itselfcyphrex-remote-mcp
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-11 the server answered initialize and tools/list without a sign-in. First answer in 125 ms.
register_agentRegister a new Cyphrex agent
check_actionRun Cyphrex check on a proposed action
log_actionLog an executed action for a Cyphrex agent
get_audit_logGet Cyphrex audit log for an agent
set_behavior_profileSet behavior profile for an agent
verify_agentFetch/verify agent details
scan_mcp_tools_listScan an upstream MCP tools/list payload for threats and diff tool snapshots
scan_mcp_tool_resultScan an upstream MCP tools/call result for PII, injection, and volume anomalies
proxy_mcp_requestProxy a JSON-RPC tools/list or tools/call request to an upstream MCP server. Cyphrex enforces threat policy before the caller receives the upstream result.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"cyphrex-mcp": {
"type": "http",
"url": "https://mcp.cyphrex.io/mcp"
}
}
}OpenAPI spec
8 paths, read 2026-10-11. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.