Cyphrex

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other
• You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

claude mcp add --transport http cyphrex https://mcp.cyphrex.io/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "cyphrex": {
      "url": "https://mcp.cyphrex.io/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

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

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• Authorization secret required HTTP header
  Your Cyphrex API key (format: Bearer cprx_live_...)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• register_agent

  Register a new Cyphrex agent

• check_action

  Run Cyphrex check on a proposed action

• log_action

  Log an executed action for a Cyphrex agent

• get_audit_log

  Get Cyphrex audit log for an agent

• set_behavior_profile

  Set behavior profile for an agent

• verify_agent

  Fetch/verify agent details

• scan_mcp_tools_list

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

• scan_mcp_tool_result

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

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

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

• 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,

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified with the GitHub account getcyphrex, which owns the repo

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 127 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 11 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32683 servers in this category
• Published to the registry more recently than 80% of the other 32683 servers in this category
• Basic checks equal to or better than 100% of the other 32683 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo