Cyphrex
REMOTE · MCP.CYPHREX.IO
Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits.
Available components
Last scanned (12 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 589 tokens (~53/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 0
- Schema quality: 42 → 53 ▼ functional
- New tool “run_aiuc1_gap_check” functional
- New tool “verify_record” functional
- 19 Oct 26 +3
- HSTS header: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Aug 26 0
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Schema quality: pass functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.cyphrex.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cyphrex.io | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 677ddd3c61e5d6269d4e9496232a2ffdced |
| SANs: *.cyphrex.io, cyphrex.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cyphrex.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| cyphrex.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cyphrex.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cyphrex.io/mcp | HTTPS enforced | 301 | https://mcp.cyphrex.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_action ~31
Run Cyphrex check on a proposed action
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | – |
| agentId | string | yes | – |
No output schema declared.
No examples provided.
get_audit_log ~35
Get Cyphrex audit log for an agent
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
log_action ~39
Log an executed action for a Cyphrex agent
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | – |
| agentId | string | yes | – |
| metadata | object | – | – |
No output schema declared.
No examples provided.
proxy_mcp_request ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| message | object | yes | – |
| upstreamAuthorization | string | – | – |
| upstreamSessionId | string | – | – |
| upstreamUrl | string | yes | – |
No output schema declared.
No examples provided.
register_agent ~37
Register a new Cyphrex agent
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| name | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
run_aiuc1_gap_check ~77
Public AIUC-1 readiness self-check. No API key. AIUC-1 readiness self-check. Not certification, and not affiliated with or endorsed by AIUC.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | – |
| string | – | – | |
| marketing_opt_in | boolean | – | – |
| send_results | boolean | – | – |
No output schema declared.
No examples provided.
scan_mcp_tool_result ~58
Scan an upstream MCP tools/call result for PII, injection, and volume anomalies
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| result | – | yes | – |
| serverUrl | string | – | – |
| toolName | string | yes | – |
No output schema declared.
No examples provided.
scan_mcp_tools_list ~48
Scan an upstream MCP tools/list payload for threats and diff tool snapshots
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| serverUrl | string | yes | – |
| tools | array | yes | – |
No output schema declared.
No examples provided.
set_behavior_profile ~31
Set behavior profile for an agent
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| profile | object | yes | – |
No output schema declared.
No examples provided.
verify_agent ~22
Fetch/verify agent details
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
No output schema declared.
No examples provided.
verify_record ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_base64 | string | – | – |
| public_key_pem | string | – | – |
| record | object | – | – |
No output schema declared.
No examples provided.
How do I install the Cyphrex MCP server?
Cyphrex is a hosted endpoint at https://mcp.cyphrex.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.cyphrex.io
claude mcp add --transport http getcyphrex-cyphrex-mcp 'https://mcp.cyphrex.io/mcp'
What is the Cyphrex MCP server?
Cyphrex is an MCP server listed in the public MCP registry as io.github.getcyphrex/cyphrex-mcp. Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits. This page covers its hosted endpoint (https://mcp.cyphrex.io/mcp).
Is the Cyphrex MCP server safe to use?
Cyphrex scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Cyphrex MCP server expose?
Cyphrex exposes 11 tools: register_agent, check_action, log_action, get_audit_log, set_behavior_profile, and 6 more. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.
Does the Cyphrex MCP server require authentication?
No. We connected to Cyphrex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cyphrex MCP server still maintained?
Cyphrex is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Cyphrex MCP server?
VerifyMCP ran 12 checks on Cyphrex, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Cyphrex: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.