io.github.lonniev/cypher-mcp
REMOTE · CYPHER-MCP.FASTMCP.APP · SCANNED SEP 20
Monetized graph answers via named Cypher queries — Tollbooth DPYC operator
Available components
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 Security57
- 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 112 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 13815 tokens (~123/item across 112 items; 112 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
- Structured output schemas are declared (52% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cypher_forget_credentials" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 113 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
How do I install the io.github.lonniev/cypher-mcp server?
io.github.lonniev/cypher-mcp is a hosted endpoint at https://cypher-mcp.fastmcp.app/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 · cypher-mcp.fastmcp.app
claude mcp add --transport http lonniev-cypher-mcp 'https://cypher-mcp.fastmcp.app/mcp'
{
"mcpServers": {
"lonniev-cypher-mcp": {
"url": "https://cypher-mcp.fastmcp.app/mcp"
}
}
} {
"servers": {
"lonniev-cypher-mcp": {
"type": "http",
"url": "https://cypher-mcp.fastmcp.app/mcp"
}
}
} [mcp_servers.lonniev-cypher-mcp] url = "https://cypher-mcp.fastmcp.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lonniev-cypher-mcp": {
"type": "remote",
"url": "https://cypher-mcp.fastmcp.app/mcp",
"enabled": true
}
}
} openclaw mcp add lonniev-cypher-mcp --url 'https://cypher-mcp.fastmcp.app/mcp' --transport streamable-http
mcp_servers:
lonniev-cypher-mcp:
url: "https://cypher-mcp.fastmcp.app/mcp" {
"McpServers": {
"lonniev-cypher-mcp": {
"Transport": "http",
"Url": "https://cypher-mcp.fastmcp.app/mcp"
}
}
} assistant mcp add lonniev-cypher-mcp -t streamable-http -u 'https://cypher-mcp.fastmcp.app/mcp'
{
"mcpServers": {
"lonniev-cypher-mcp": {
"type": "http",
"url": "https://cypher-mcp.fastmcp.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 0
- Stability: fail → pass ▲ security
- 13 Sept 26 +28
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 112 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
- Schema quality: unverified → fail ▼ functional
- Schema quality: 727 → 123 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: excellent → good functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 12 Sept 26 −28
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 123 → 727 ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: good → excellent functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 6 Sept 26 +28
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 112 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
- Schema quality: unverified → fail ▼ functional
- Schema quality: 727 → 123 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: excellent → good functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 5 Sept 26 −28
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 123 → 727 ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: good → excellent functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Sept 26 0
- Stability: pass → fail ▼ security
- 31 Aug 26 +14
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 112 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
- Schema quality: unverified → fail ▼ functional
- Schema quality: 727 → 123 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: excellent → good functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Aug 26 −14
- Tool safety: pass → unverified ▼ security
- Stability: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 123 → 727 ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: good → excellent functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 20 Sept 2026 · Probed https://cypher-mcp.fastmcp.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fastmcp.app | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 17 Jun 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | a1583bafd89c7b58780ef1a0a0d2ad7 |
| SANs: *.fastmcp.app | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cypher-mcp.fastmcp.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| fastmcp.app. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cypher-mcp.fastmcp.app/mcp | Verified | 200 | |
| http (plaintext) | http://cypher-mcp.fastmcp.app/mcp | HTTPS enforced | 301 | https://cypher-mcp.fastmcp.app/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 →
cypher_symbol_provenance ~61
Pivot to a code symbol — its service, capabilities, issues, decisions, invariants.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| fqn | string | yes | The symbol's fully-qualified name. |
| npub | string | – | – |
No output schema declared.
No examples provided.
cypher_symbols_in_service ~45
List a service's indexed symbols.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| npub | string | – | – |
| repo_name | string | yes | Repository name. |
No output schema declared.
No examples provided.
cypher_unpublish_tool ~93
Operator-only: retire a previously published named tool. The catalog query itself is kept (still runnable via ``execute_query_by_key``); only its projected named tool is removed. Reconnect to see it disappear from the tool list.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| key | string | yes | – |
| npub | string | – | Required. The operator's npub (npub1...). |
Structured output declared, but exposes no named fields.
No examples provided.
cypher_update_coupon ~167
Patch a coupon's editable fields. Pass only the fields you want to change. To set a cap to unlimited (NULL in the schema), pass ``clear_uses_per_patron=true`` or ``clear_total_uses=true``. Renaming the code is allowed — existing patron redemption rows survive (they key on coupon id). RESTRICTED to operator — requires proof.
| Name | Type | Req | Description |
|---|---|---|---|
| clear_total_uses | boolean | – | – |
| clear_uses_per_patron | boolean | – | – |
| coupon_id | string | yes | – |
| discount_percent | – | – | – |
| dpop_token | string | – | – |
| name | – | – | – |
| total_uses | – | – | – |
| uses_per_patron | – | – | – |
| valid_from | – | – | – |
| valid_until | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
cypher_update_operator_credential ~182
Add or update a single operator secret field. Merges into the operator's stored credentials without touching the others — the field-level counterpart to re-delivering the whole bundle over Secure Courier. Use it to rotate one secret (a reissued ``btcpay_api_key``, say) without restating the six you did not change, where any field omitted from a courier reply is destroyed. The value is never echoed back. RESTRICTED to the operator — requires proof (nsec-signed kind-27235 or a cached dpop_token phrase); patron proofs are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | yes | Operator proof for this tool. |
| field | string | yes | The operator credential field to set. Must be declared in the operator's credential template. |
| value | string | yes | The value to store. |
Structured output declared, but exposes no named fields.
No examples provided.
cypher_update_patron_credential ~218
Add or update a single patron credential field. Merges into existing stored credentials without affecting other fields. Useful for setting an account identifier after OAuth, changing a default brain, etc. Free. Proof of npub ownership is required — this is a write to the patron's sensitive credential vault.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | yes | Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… |
| field | string | yes | The credential field name to set. |
| npub | string | yes | The patron's Nostr public key (npub1...). |
| value | string | yes | The value to store. |
Structured output declared, but exposes no named fields.
No examples provided.
cypher_update_query ~117
Operator-only: update an existing named Cypher query template. Same shape as create_query, but the key must already exist.
| Name | Type | Req | Description |
|---|---|---|---|
| access_mode | string | – | – |
| cypher_template | string | yes | – |
| description | string | – | – |
| dpop_token | string | – | – |
| key | string | yes | – |
| npub | string | – | Required. The operator's npub (npub1...). |
| param_schema | – | – | – |
| row_limit | integer | – | – |
| timeout_ms | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
cypher_upsert_capability ~96
Record a cross-cutting service Capability and one of its owners.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| keywords | string | yes | Comma-joined search keywords for forward-map resolution. |
| name | string | yes | Capability name, e.g. 'Secure Courier'. |
| npub | string | – | – |
| owner_repo | string | yes | Repo of an owning Service (multi-owner: call again per owner). |
No output schema declared.
No examples provided.
cypher_upsert_patent_element ~116
Record a patent reference numeral as a node.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_family | string | yes | Claim family, e.g. 'Nostr Identity & Credential Exchange'. |
| dpop_token | string | – | – |
| figures | string | yes | Figures the element appears in, e.g. '5' or '1,4'. |
| name | string | yes | Element name from the reference-numeral schedule. |
| npub | string | – | – |
| ref | integer | yes | Patent reference numeral, e.g. 610. |
No output schema declared.
No examples provided.
cypher_upsert_pull_request ~259
Upsert the live state of a GitHub PR into the graph.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | GitHub login that opened the PR. |
| base_ref | string | – | Base branch the PR targets (e.g. 'main'). |
| created_at | string | – | GitHub creation timestamp (ISO-8601); a graph timestamp is used if omitted. |
| dpop_token | string | – | – |
| draft | boolean | – | True while the PR is a draft (in-progress, not yet up for review). |
| head_ref | string | – | Head branch of the PR (e.g. 'agent/fix-123'). |
| head_sha | string | – | Head commit SHA (changes on each synchronize). |
| merged_at | string | – | GitHub merge timestamp (ISO-8601), or null if not merged. |
| npub | string | – | – |
| number | integer | yes | The PR number (node identity). |
| repo_name | string | yes | Repository name. |
| state | string | yes | Lifecycle state: 'open' | 'closed' (merged PRs are closed with merged_at set). |
| title | string | yes | PR title. |
| url | string | yes | The PR's canonical GitHub URL. |
No output schema declared.
No examples provided.
cypher_what_realizes_capability ~48
Find the symbols that implement a capability.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| name | string | yes | Capability name. |
| npub | string | – | – |
No output schema declared.
No examples provided.
cypher_which_service_handles ~60
Find which service handles a given intent.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| keyword | string | yes | Intent keyword, e.g. 'npub proof', 'vault', 'pricing'. |
| npub | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.lonniev/cypher-mcp server?
io.github.lonniev/cypher-mcp is listed in the public MCP registry as io.github.lonniev/cypher-mcp. Monetized graph answers via named Cypher queries, Tollbooth DPYC operator. This page covers its hosted endpoint (https://cypher-mcp.fastmcp.app/mcp).
Is the io.github.lonniev/cypher-mcp server safe to use?
io.github.lonniev/cypher-mcp scores 75 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 io.github.lonniev/cypher-mcp server expose?
io.github.lonniev/cypher-mcp exposes 112 tools: cypher_check_balance, cypher_purchase_credits, cypher_check_payment, cypher_restore_credits, cypher_account_statement, and 107 more. Their descriptions and schemas cost roughly 13,088 tokens of context every time the server is loaded.
Does the io.github.lonniev/cypher-mcp server require authentication?
No. We connected to io.github.lonniev/cypher-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.lonniev/cypher-mcp server still maintained?
io.github.lonniev/cypher-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.