cypher-mcp

Reviewed 21h ago.

• tools: 112 tools scanned
• metadata: scanned

No findings.

Tools (112)

• cypher_check_balance

  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 required. Proof of npub ownership is required to prevent anyone-with-the-registry from enumerating balances.

• cypher_purchase_credits

  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.

• cypher_check_payment

  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.

• cypher_restore_credits

  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 their behalf. Use cases: cold-start vault races during check_payment, ncred delivery hiccups, patrons closing Top-Off sheets before settle, any infrastructure incident that left an invoice settled at BTCPay but uncredited on the operator's ledger. Idempotent — if the invoice is already credited (in the patron's ``credited_invoices``), returns success with credits_granted=0.

• cypher_account_statement

  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 ownership is required to prevent statement-scraping of arbitrary patrons.

• cypher_account_statement_infographic

  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`` before any cost is incurred.

• cypher_report_issue

  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 attributed to you, not the operator. Costs a small fee (a free write to an issue tracker would be abused). The report is PUBLIC and goes to the maintainers' normal triage; nothing is verified here. Returns the filed issue's repo, number, and url. If this operator has not enabled field reports, returns an "issue reporting not configured" situation and you are not charged.

• cypher_service_status

  Check the health and configuration of this service. Free.

• cypher_get_operator_onboarding_status

  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.

• cypher_get_patron_onboarding_status

  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 because credential presence is sensitive information about the patron's setup.

• cypher_session_status

  Check operator readiness. Returns the operator lifecycle state and clear guidance on what to do next. Free. Lifecycle states: - ready: Vault AND pricing model verified on this call. Proceed with tool calls — this is the answer the moment the vault is up. - warming_up: Persistence could not be reached on this call (a transient failure, seen, not assumed). Retry; the next call completes the bootstrap. Never reported on a clock. - misconfigured: Persistence rejected a query with a permanent SQL error (permission denied, missing relation). Paid tools will fail until the operator repairs the database — retrying does not help. - quota_exceeded: The persistence provider (Neon) answered HTTP 402 — the operator's database has exhausted its compute/storage quota, so the books are locked for billing. Paid tools fail; retrying does NOT help. The operator's Authority must restore capacity (upgrade the plan or wait for the quota reset). Free tools remain available. - not_registere

• cypher_request_credential_channel

  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 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

• cypher_receive_credentials

  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, dpop_token)`` and the tool drains ONLY the rendezvous relay that channel was pinned to. Every popped DM with the wrong session phrase is deleted and its sender is NACK'd; the first DM with the matching phrase is accepted (ACK'd) and the scan stops. If none match, the queue is drained and a ``courier_not_found`` result is returned. Do NOT poll, loop, or retry. If a credential_card (ncred1...) is provided, it is redeemed directly without any relay access (dpop_token not required for that path). On success, the payment processor client is reinitialized from the new credentials — no server restart needed.

• cypher_forget_credentials

  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.

• cypher_update_patron_credential

  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.

• cypher_update_operator_credential

  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.

• cypher_delete_patron_credential

  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.

• cypher_delete_operator_credential

  Remove a single operator secret field. Deletes one key from the operator's encrypted credential blob without touching the others — the field-level counterpart to ``forget_credentials``, which wipes the whole row. Use it to retire a leftover after an SDK cutover (a Prefect key after Modal, or a stored but untemplated orphan like ``anthropic_api_key``) without taking the operator down for a full re-delivery. Stored-but-untemplated fields are first-class: the delete is keyed on what is vaulted, not on what the current template declares. Idempotent — already-absent fields report ``removed: false`` without rewriting the vault. RESTRICTED to the operator — requires proof (nsec-signed kind-27235 or a cached dpop_token phrase); patron proofs are rejected. A deletion is as destructive as a write.

• cypher_get_patron_credential_fields

  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 configured and how old each one is. Free. Proof of npub ownership is required: the list of configured fields is itself sensitive (reveals which integrations a patron has set up).

• cypher_request_npub_proof

  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_channel`` instead. Sends a challenge DM that the patron must sign and reply to using their Nostr client. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user to check their Nostr client and reply to the challenge. Wait for the user to confirm they have replied before calling ``receive_npub_proof``. Do NOT poll or retry — each ``receive_npub_proof`` call destructively drains the relay mailbox. **Returns** a ``dpop_token`` — the one-time challenge nonce shown in the DM. Pass it to ``receive_npub_proof`` to collect the reply. It is a matching token, not a credential: on its own it authorizes nothing. **Lifecycle:** ``receive_npub_proof`` returns the proof gr

• cypher_receive_npub_proof

  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_token)`` — the ``dpop_token`` being the value returned by ``request_npub_proof``. The tool drains ONLY the pinned rendezvous relay that challenge was published on, stopping at the DM whose phrase matches. Mismatched DMs are deleted and NACK'd (without revealing the expected phrase). If called before the user replies, their message will never be found. Do NOT poll, loop, or retry. The signed DM itself proves npub ownership (the patron's nsec signed it). On success, returns a new ``dpop_token``: an Operator-signed **proof grant envelope** ``{"grant": …, "nonce": …}`` bound to the patron, this challenge, and the duration the patron named. The calling application MUST remember that whole string

• cypher_check_proof_status

  Check whether a proof grant 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. Expiry is read from the grant itself; the only store consulted is the patron's revocation watermark. Free, no side effects — touches no relay.

• cypher_oracle_how_to_join

  Get DPYC onboarding instructions from the Oracle. Free.

• cypher_oracle_get_tax_rate

  Get the current DPYC certification tax rate. Free.

• cypher_oracle_lookup_member

  Look up a DPYC community member by npub. Free.

• cypher_oracle_about

  Describe the DPYC ecosystem via the Oracle. Free.

• cypher_oracle_network_advisory

  Get active network advisories from the Oracle. Free.

• cypher_check_authority_balance

  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 balance. Free.

• cypher_get_pricing_model

  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.

• cypher_set_pricing_model

  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.

• cypher_reset_pricing_model

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

• cypher_request_adoption

  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 request MCP-to-MCP. The Authority records it as pending; its owner approves on their own time. Poll ``adoption_status`` for progress; the operator flips to ``ready`` once the Authority provisions it.

• cypher_adoption_status

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

• cypher_restore_neon_schema

  Prepare this operator's database schema again, ignoring the breadcrumb. Diagnostic / recovery tool for when Neon keeps answering 4xx and the operator suspects a table or grant is missing. Every statement is idempotent, so a clean re-run is harmless; the breadcrumb is rewritten at the end. Returns one step per concern, with Neon's own error text inline for any that failed. RESTRICTED to operator — requires proof (nsec-signed).

• cypher_list_canonical_identities

  Return canonical (tool_id, mcp_name, …) for every tool the wheel exposes. 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. Includes both ToolIdentity-seeded tools and any UUID recorded by ``@paid_tool`` that is missing from the registry. The latter appear with ``registered: false`` (and in the top-level ``unregistered`` array) so Reconcile can flag deploy drift instead of silently reporting clean when a live tool was never seeded (#174). If the operator renames a function or rebrands a slug, the mcp_name in this output changes but tool_id stays. That's the whole point of the canonical-UUID design. Also diffs the live FastMCP wire surface against the registry. Tools exposed on the wire but absent from the registry appear in ``unregistered`` so Reconcile can flag deploy drift instead of silently under-

• cypher_get_nostr_profile

  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.

• cypher_publish_nostr_profile

  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 it to public relays. The signature is the authorization — no proof token, no key custody. Free.

• cypher_check_price

  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.

• cypher_list_constraint_types

  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.

• cypher_mint_coupon

  Create a new operator-owned discount coupon. The coupon owns its binding: ``tool_ids`` names the tools it discounts, and re-pricing a tool never touches it. A coupon bound to no tool discounts nothing, however many patrons redeem it.

• cypher_list_coupons

  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.

• cypher_update_coupon

  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). ``tool_ids`` replaces the coupon's binding — tool ids or MCP tool names, ``["*"]`` for every paid tool, ``[]`` to unbind it. RESTRICTED to operator — requires proof.

• cypher_delete_coupon

  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.

• cypher_redeem_coupon

  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 credits required. Requires proof of ``npub``. Idempotent: redeeming the same code twice returns the existing redemption.

• cypher_list_my_coupons

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

• cypher_forget_coupon

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

• cypher_notarize_ledger

  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.

• cypher_get_notarization_proof

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

• cypher_list_notarizations

  List recent Bitcoin notarization records.

• cypher_execute_query_by_key

  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 can call that directly instead. Billing note: you are charged only for a delivered answer. If the key is unknown, the parameters are invalid, or the query fails, the call raises and your debit is rolled back (no charge for value not delivered).

• cypher_public_factory_stats

  Aggregate-only factory stats for the unauthenticated landing pages. Free — no credits, no npub proof. Returns counts only (capabilities, invariants, issues, services, symbols), the resolved_via mix (graph | scoped-grep | wide-grep), and a last-activity timestamp. Never returns issue titles, symbol paths, or npubs. Hard-cached in-process (~5 min) so a sleeping AuraDB free tier is not woken on every page view. Safe for cold Bolt: failures return an empty available=false payload rather than raising.

• cypher_create_query

  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.

• cypher_update_query

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

• cypher_get_query

  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_query``. Omitted if the operator's Neo4j credentials aren't delivered yet (best-effort; the raw template is always present to paste).

• cypher_list_queries

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

• cypher_delete_query

  Operator-only: delete a catalog entry by key.

• cypher_publish_tool

  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 but starts **unpriced** — it appears in Pricing Studio like any new tool; set its price there. Until priced, calls return "not priced yet (TBD)". Patrons then call it by name with typed params instead of ``execute_query_by_key``. The key must be a valid tool identifier (^[a-z][a-z0-9_]*$). Reconnect to see the new tool in the tool list.

• cypher_unpublish_tool

  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.

• cypher_anchor_symbol

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

• cypher_assert_invariant

  Record an enforceable code invariant.

• cypher_assert_rationale

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

• cypher_audit_what_changed_since

  Answer what changed on a capability since a given time.

• cypher_audit_what_contradicts

  Answer what contradicts a capability's assertions or guarding invariants.

• cypher_audit_what_derived_from

  Answer what sources a capability was derived from.

• cypher_audit_what_guards

  Answer which invariants guard a capability.

• cypher_audit_who_authorized

  Answer who authorized a capability's authoritative why.

• cypher_audit_why_exists

  Answer why a capability exists with PROV-attributed assertions and gaps.

• cypher_authorize_capability_why

  Author the authoritative why for a capability.

• cypher_bind_capability_to_symbol

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

• cypher_bind_rationale_to_symbol

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

• cypher_capability_patents

  Show a capability's patent grounding.

• cypher_claim_issue

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

• cypher_context_pack

  Return the code-orienteering scope for an intent keyword.

• cypher_explain_capability

  Explain why a capability exists and where it lives.

• cypher_explain_patent_element

  Show what a patent reference numeral describes.

• cypher_factory_resolution_stats

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

• cypher_find_airline_flights

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

• cypher_guard_invariant_symbol

  Register a symbol an invariant guards.

• cypher_index_symbol

  Index a code symbol as belonging to a service.

• cypher_invariant_provenance

  Explain an invariant and what it guards.

• cypher_issue_provenance

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

• cypher_link_capability_consumer

  Record that a service consumes a capability.

• cypher_link_capability_to_patent

  Ground a capability in a patent reference numeral.

• cypher_link_invariant_to_patent

  Ground an invariant in a patent reference numeral.

• cypher_link_issue_to_capability

  Attach an issue to the capability it is about.

• cypher_link_pr

  Attach the fix PR to its issue via the FIXES edge.

• cypher_link_root_cause

  Point an issue at the code symbol that caused it.

• cypher_list_capabilities

  List every capability for semantic intent-matching.

• cypher_list_invariants

  List every enforceable invariant.

• cypher_list_issues

  List every triaged issue for the Issues register.

• cypher_list_patent_elements

  List every filed patent reference numeral.

• cypher_list_pull_requests

  List every mirrored pull request for the Pull Requests register.

• cypher_mark_funding_state

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

• cypher_mark_invariant_contradiction

  Mark two invariants as contradictory.

• cypher_note_rejection

  Record why the Porter rejected an issue.

• cypher_pr_provenance

  Fetch a PR's fixes and the intentions it enforces for the PR dossier.

• cypher_recent_activity

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

• cypher_record_scope

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

• cypher_record_triage

  Record the Porter's triage of a GitHub issue.

• cypher_register_service

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

• cypher_retire_funding_block

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

• cypher_route_rejection

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

• cypher_routing_history

  Show which repos have declined an issue and why.

• cypher_service_provenance

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

• cypher_suggest_capability_why

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

• cypher_symbol_provenance

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

• cypher_symbols_in_service

  List a service's indexed symbols.

• cypher_upsert_capability

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

• cypher_upsert_patent_element

  Record a patent reference numeral as a node.

• cypher_upsert_pull_request

  Upsert the live state of a GitHub PR into the graph.

• cypher_what_realizes_capability

  Find the symbols that implement a capability.

• cypher_which_service_handles

  Find which service handles a given intent.