Cypher Mcp

Check a patron's credit balance at this operator. This is the patron's spending balance — credits purchased via Lightning for tool calls at this operator. For the operator's own balance at the Authority (needed to certify patron purchases), use authority_check_balance instead. Free — no credits re

Buy credits via Bitcoin Lightning. Creates a Lightning invoice. Pay it with any Lightning wallet, then call check_payment to confirm. Proof of npub ownership is required so credits land in the correct ledger. Free — no credits required to call.

Check the payment status of a Lightning invoice. Call after paying the invoice from purchase_credits. Free — no credits required. Proof of npub ownership is required to prevent credit-grant front-running by an observer of the invoice ID.

Credit a patron's ledger from a BTCPay-settled invoice. **RESTRICTED to the operator** — the operator owns the books and is the only party who can issue a manual credit grant. Patrons who believe they paid but never got credits must escalate to the operator's support, who then invokes this tool on

Generate a patron's account statement at this operator. Returns the patron's purchase history, active credit tranches, per-tool usage breakdown, and recent daily usage logs. This is the patron's spending account — not the operator's Authority tax balance. Free — no credits consumed. Proof of npub

Generate a visual SVG infographic of your account statement. Returns the same data as account_statement, rendered as a dark-themed SVG graphic with balance hero, metrics cards, health gauge, tranche table, and tool usage breakdown. Costs 1 api_sat per call. Proof is verified by ``debit_or_deny`` be

File a field report about this service as a GitHub issue on the operator's repo. Found a tool's metadata or response wrong or confusing? Report it where the tool lives. The **author of record is your npub** — no npub / no proof, no issue — and it is stamped into the issue so the report is attribute

Check the health and configuration of this service. Free.

Report this operator's configuration readiness. Shows which operator settings are configured, which are missing, and how to deliver each missing value. For patron-level credential status, use get_patron_onboarding_status instead. Free.

Report a patron's credential readiness for this operator. For set-once services (eXcalibur, TheBrain), shows which patron secrets are configured and which are missing. For dynamic/OAuth2 services (Schwab), reports that no patron credentials are needed. Free. Proof of npub ownership is required beca

Check operator readiness. Returns the operator lifecycle state and clear guidance on what to do next. Free. Lifecycle states: - ready: Operator is warm and fully operational — vault AND pricing model verified. Proceed with tool calls. - warming_up: Operator is initializing (cold start). Try a too

Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 servi

Pick up credentials from the Secure Courier. Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is ``receive_npub_proof``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response you want with ``(sender_npub, service,

Delete vaulted credentials for a specific service and npub. For operator credentials, pass the operator's own npub. For patron credentials, pass the patron's npub. Always requires proof of npub ownership — a deletion is as destructive as a write.

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 credenti

Remove a single patron credential field. Deletes one field from stored credentials without affecting other fields. Free. Proof of npub ownership is required — this is a write to the patron's sensitive credential vault.

List stored patron credential field names (not values). Returns the names of fields stored for a patron, plus each field's ``delivered_at`` ISO-8601 timestamp when known (null for secrets vaulted before timestamps were recorded). Values are never exposed — use this to verify which fields are config

Request npub ownership proof from a patron via Nostr DM. This is the npub-OWNERSHIP-PROOF flow — use it when a call returns ``proof_required``. It proves the caller controls an npub; it does NOT deliver any service secret. To hand an operator its API keys or OAuth secrets, use ``request_credential_

Receive npub ownership confirmation from a patron. Completes the npub-OWNERSHIP-PROOF flow (the credential-delivery counterpart is ``receive_credentials``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response with ``(patron_npub, dpop_

Check whether a previously-cached dpop_token is still valid. Mirrors ``check_oauth_status`` for the npub-proof flow: a calling agent can ask "will my next paid call accept this dpop_token?" before burning credits on a guaranteed failure. Free, no side effects — does not evict the cache or touch re

Get DPYC onboarding instructions from the Oracle. Free.

Get the current DPYC certification tax rate. Free.

Look up a DPYC community member by npub. Free.

Describe the DPYC ecosystem via the Oracle. Free.

Get active network advisories from the Oracle. Free.

Check this operator's tax balance at the Authority. Returns the sats available for certifying patron credit purchases. When this balance reaches zero, patron top-ups cannot be certified and the operator must call purchase_credits on the Authority. This is the operator's own funding — not a patron

Get the active pricing model for this operator. Free. If no model exists, self-initializes a scaffold with all registered tools at 0 sats. No economic data from code.

Set the active pricing model. RESTRICTED to operator. Requires a valid proof (Schnorr-signed kind-27235 event) proving the caller holds the operator's nsec.

Erase all pricing models and restore a viable default. Deletes every stored model, then self-initializes a fresh one from the tool registry — all tools at 0 sats with proper UUIDs. Returns the new model. RESTRICTED to operator — requires proof (nsec-signed).

Ask a chosen Authority to adopt this operator (deferred courtship). RESTRICTED to the operator — requires proof the caller controls this operator's npub. Resolves the Authority's MCP endpoint from the community registry, mints an inline ownership proof with this operator's nsec, and delivers the re

Check this operator's adoption-request status at a chosen Authority. Free. Polls the Authority MCP-to-MCP for the status of this operator's request (pending / approved / rejected / provisioned).

Re-run ``ensure_schema()`` on every NeonVault this operator uses. Diagnostic / recovery tool for the case where the Neon HTTP SQL API is returning persistent 4xx errors and the operator suspects the schema isn't there or grants are wrong. Idempotent — uses ``CREATE TABLE IF NOT EXISTS`` so a succes

Return canonical (tool_id, mcp_name, …) for every registered tool. The authoritative source for any client (Studio, agents, FE) that needs to know how this MCP identifies its tools. Reconcile uses this output to UUID-join against the stored pricing model — no name-based UUID derivation, no guessing

Read an npub's public Nostr profile (NIP-01 kind-0 metadata). Free, no proof — the data is already public on relays. Returns the latest metadata fields (name, display_name, about, picture, banner, nip05, website, lud16) or an empty profile if none is published.

Publish a CLIENT-SIGNED kind-0 profile to relays for an npub. The wheel never holds a patron nsec. The frontend signs the kind-0 metadata event with the patron's session key or a NIP-07 extension and passes the signed event (JSON) here; the wheel verifies the signature matches the npub, then relays

Preview the effective cost of a tool call. Shows the base cost and any constraint effects (discounts, free trials, surge pricing). Free — no credits required.

List all available constraint types and their parameter schemas. Returns the type, category, description, and parameter specs for every constraint that can be used in a pricing pipeline. Free — no credits required.

Create a new operator-owned discount coupon.

List every coupon this operator has minted (newest first). Each row carries the current ``times_redeemed`` counter — the Studio renders a progress bar from this against ``total_uses``. RESTRICTED to operator — requires proof.

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

Delete a coupon. Cascades to all patron redemptions. Any chain step referencing the deleted coupon_id becomes a no-op (the constraint returns neutral on unknown ids) — the Studio surfaces orphan references as warnings. RESTRICTED to operator — requires proof.

Claim a coupon by its name (the code the operator shared). Looks up the operator's coupon by ``code``, validates the window and total cap, and records a per-patron redemption row. Subsequent paid tool calls on this MCP auto-apply the discount until ``uses_per_patron`` is exhausted. Free — no credi

List the coupons this patron has redeemed on this operator. Returns both active and exhausted redemptions with a per-row ``status`` (``active`` / ``window_closed`` / ``patron_limit`` / ``total_limit``). Free — requires proof of ``npub``.

Remove a coupon from this patron's redemption list. Cosmetic only — the coupon itself still exists at the operator, and the patron can re-redeem the same code later while the window allows. Free — requires proof of ``npub``.

Build a Merkle tree of all patron balances and submit the root to Bitcoin via OpenTimestamps. Operator-only background task. Bitcoin confirmation takes 1-6 hours. Free — no credits required.

Generate a Merkle inclusion proof that a patron's balance was included in a Bitcoin-notarized snapshot.

List recent Bitcoin notarization records.

Execute a published, parameterized Cypher query by its key. You supply the key of an operator-published query plus its parameters. The operator owns the query text; you never see or write raw Cypher. If the operator has published a query as a named tool (e.g. ``cypher_find_airline_flights``), you c

Operator-only: publish a new named Cypher query template. The template must reference each declared parameter as $name (binding, not interpolation). param_schema maps param name -> {"type": ..., "required": true|false}; types: string, int, float, bool, list.

Operator-only: update an existing named Cypher query template. Same shape as create_query, but the key must already exist.

Operator-only: fetch one catalog entry (template + schema + metadata). Includes ``edit_url`` — a one-click deep link into the hosted Neo4j Browser that pre-targets this operator's AuraDB and loads the template in EDIT mode, so the analyst refines it in Neo4j's own UI and saves it back with ``update

Operator-only: list this operator's published query keys.

Operator-only: delete a catalog entry by key.

Operator-only: expose a catalog query as a named, typed MCP tool. Projects the published query as a first-class tool named ``cypher_<key>`` whose flat, typed parameters come from the query's param schema (e.g. ``cypher_find_airline_flights(from_city, to_city)``). The tool is registered immediately

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.

Record where a symbol lives so future triage scopes its grep.

Record an enforceable code invariant.

Record the Journeyman's rationale for a fix (unverified provenance).

Author the authoritative why for a capability.

Attach a capability to one of the symbols that implement it.

Attach the Journeyman's rationale to a specific code symbol.

Show a capability's patent grounding.

Mark an issue as actively being worked at the start of an agent's turn.

Return the code-orienteering scope for an intent keyword.

Explain why a capability exists and where it lives.

Show what a patent reference numeral describes.

Report how issues were located, to measure grep-scope shrinkage.

Find airline routes between two cities (named-tool smoke test).

Register a symbol an invariant guards.

Index a code symbol as belonging to a service.

Explain an invariant and what it guards.

Fetch an issue's GitHub URLs and provenance chain for browser click-through.

Record that a service consumes a capability.

Ground a capability in a patent reference numeral.

Ground an invariant in a patent reference numeral.

Attach an issue to the capability it is about.

Attach the fix PR's GitHub URL to its issue.

Point an issue at the code symbol that caused it.

List every capability for semantic intent-matching.

List every enforceable invariant.

List every triaged issue for the Issues register.

List every filed patent reference numeral.

Reflect an LLM-credit outage (or its clearance) in the intention graph.

Record why the Porter rejected an issue.

List every domain object changed within a date window, across all node types.

Record the actionable spec and the code-location method for an issue.

Record the Porter's triage of a GitHub issue.

Register a repo as a Service node in the factory graph.

Retire a stale funding block to a historical record when its item closes.

Route a target's rejection reason back to the origin issue.

Show which repos have declined an issue and why.

Pivot to a service — its capabilities, symbols, and issues.

Offer the Journeyman's read on why a capability exists.

Pivot to a code symbol — its service, capabilities, issues, decisions, invariants.

List a service's indexed symbols.

Record a cross-cutting service Capability and one of its owners.

Record a patent reference numeral as a node.

Find the symbols that implement a capability.

Find which service handles a given intent.