Cyphrex MCP Server

by getcyphrex Your server? Claim it

answering

Cyphrex is answering right now. Last checked 7 min ago. It exposes 11 tools.

Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

332 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 October 2026. No other catalogue keeps this.

29 Oct 2 tools appeared run_aiuc1_gap_check, verify_record

29 Oct a tool disappeared run_aiuc1_gap_check

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add cyphrex-mcp --transport http https://mcp.cyphrex.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.cyphrex.io/mcp

~/.codex/config.toml

[mcp_servers.cyphrex-mcp]
url = "https://mcp.cyphrex.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "cyphrex-mcp": {
      "url": "https://mcp.cyphrex.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "cyphrex-mcp": {
      "type": "http",
      "url": "https://mcp.cyphrex.io/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

scan

scan_mcp_tool_result

Scan an upstream MCP tools/call result for PII, injection, and volume anomalies

scan_mcp_tools_list

Scan an upstream MCP tools/list payload for threats and diff tool snapshots

verify

verify_agent

Fetch/verify agent details

verify_record

Check a record or export bundle. Reports the signature, a public timestamp when one is present, and an RFC 3161 timestamp valid when a token is attached. A record also reports its hash chain. A bundle reports file_hashes against the manifest. Each part is pass, fail, not_present, or not_checked. A signature that verifies only with a caller-supplied key that is not Cyphrex's is pass_supplied_key. No API key.

action

check_action

Run Cyphrex check on a proposed action

aiuc1

run_aiuc1_gap_check

Public AIUC-1 readiness self-check. No API key. AIUC-1 readiness self-check. Not certification, and not affiliated with or endorsed by AIUC.

audit

get_audit_log

Get Cyphrex audit log for an agent

behavior

set_behavior_profile

Set behavior profile for an agent

log

log_action

Log an executed action for a Cyphrex agent

proxy

proxy_mcp_request

Proxy 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.

register_agent

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.cyphrex.io/mcp	streamable-http	answering	308 ms	7 min ago

Alternatives to Cyphrex

same job, measured the same way

Occasio

by occasiolabs

Tamper-evident, Sigstore-signed audit trail for Claude Code agents.

94 installs/wk local only

Agent Receipts

by dropwatchhq

Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.

3 tools answering

ai-audit-trail

by sundsoffice-tech

Tamper-evident audit trails for AI agents — Ed25519-signed, hash-chained, EU AI Act ready.

172 installs/wk local only

Ccs

by correctover

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

local only

Tethered Trust

by tetheredtrust

Compatibility checks for AI agents before they buy or install: verdicts, evidence, receipts.

18 tools answering

Proof Layer

by world-999-labs

Signed, hash-chained provenance receipts for AI agent actions.

39 installs/wk local only

Fidren

by fidren

Checks a counterparty before an AI agent pays: what the evidence supports, and for how much.

1 tools answering

Tersign Evidence

by tersignhq

The record layer for the machine age: counter-signed receipts and agent action records.

472 installs/wk local only

Cyphrex — questions

Answers built from our own checks of this server.

What can Cyphrex do?

It exposes 11 tools, read directly from the server on our last check. Among them: check_action, get_audit_log, log_action, proxy_mcp_request, register_agent, run_aiuc1_gap_check and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Cyphrex mostly used for?

Its tools cluster around scan and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Cyphrex 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 332 ms. The bar chart above shows every period we have measured.

Is Cyphrex still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Cyphrex?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Cyphrex need an API key?

No. Cyphrex completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Cyphrex?

It answers our handshake in 332 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.