Cypher MCP server

cypher-mcp

Monetized graph answers over Bitcoin Lightning. A Tollbooth-DPYC Operator that sells priced answers from a graph — operator-authored, parameterized, named Cypher query templates — not raw database access.

The OSS Neo4j MCP servers are a free pipe to a database the operator separately expenses (Neo4j invoice) and separately bills for (Stripe stack). cypher-mcp collapses infrastructure cost, application billing, and access control into one metered MCP surface: the operator stops selling seats and starts selling answers, settled in sats, with no Stripe stack and no Neo4j invoice passed to the customer.

Live at https://cypher-mcp.fastmcp.app/mcp.

How it works

Two planes, cleanly separated:

every other DPYC operator. It never knows a graph exists.

• Settlement / identity plane — Neon + Nostr + Tollbooth, shared with

(graph.py), opened and torn down per request (no pool). The backing store is an implementation detail invisible to patrons, so it can be swapped without changing the MCP surface.

• Value-delivery plane — Bolt → Neo4j, sealed inside the tool handlers

Three conceptual layers:

Status: live, with named tools. L1 + L2 are shipped and serving real,

billed answers — an operator adopted by an Authority, AuraDB-backed, with

refund-on-raise verified end to end. **Named tools are now live (L3 tool

synthesis): an operator can publishtool(key) to project a query as a

first-class, typed tool (e.g. cypherfindairlineflights(fromcity,

tocity)), priced individually in Pricing Studio. Per-key parametric pricing

formulas* remain a later step — see CHANGELOG.md.

Tools

Patron (priced):

supply only parameters; the operator owns the query text, and parameters bind as Cypher $params (never string-interpolated). You're charged only for a delivered answer — an unknown key, invalid parameters, or a failed query rolls back the debit (refund-on-raise).

• cypherexecutequerybykey(key, params) — run a published query. You

Plus the standard DPYC surface from the wheel: cyphercheckbalance, cyphercheckprice, cypherpurchasecredits, Secure Courier, npub proof, Oracle delegation, account statements, constraint-based dynamic pricing, etc.

Operator-only (restricted, unpriced) — the authoring plane:

cypherlistqueries / cypherdeletequery

• cyphercreatequery / cypherupdatequery / cyphergetquery /

a first-class, typed named tool (or retire it). See Named tools below.

• cypherpublishtool(key) / cypherunpublishtool(key) — project a query as

Raw Cypher never reaches patrons — only named, parameterized templates.

Authoring in Neo4j's own UI — no second editor to learn

A DB-analyst refines templates in Neo4j Browser, not in a bespoke tool. cyphergetquery(key) returns the template plus an editurl — a deep link into the hosted Neo4j Browser (browser.neo4j.io) that pre-targets the operator's AuraDB and loads the statement in edit mode (cmd=edit). Refine it with autocomplete, run-to-test, visualization, and PROFILE; then save it back with cypherupdatequery. The template is just a string flowing over MCP — no files, no desktop, no exported bundles. The link carries the DBMS URI but never the password, and getquery is operator-only, so neither ever reaches a patron.

Named tools — publish a query as its own tool

Shortened. The full README is on GitHub.