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

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 their behalf. Use cases: cold-start vault races during check_payment, ncred delivery hiccups, pat

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.

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.

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)

Check the health and configuration of this service. Free.

Echo what the client sent with this request. Free. Reports the URL path and query, the headers, the cookies and the MCP request ``_meta``. Values are SHA-256 fingerprints, so nothing a client sends is repeated back; equal fingerprints mean equal values. Call it from two conversations and compare: a value that stays the same within one and changes between them identifies the conversation.

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

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

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

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 poppe

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 credential vault.

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 ec

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.

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

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 fi

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

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

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.

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

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 request MCP-to-MCP. The Authority records it as pending; its owner approves on their own time. Poll

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

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

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 i

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

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

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

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

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.

The live board — every hive, every bee, and when to ask again. Poll this rather than guessing a cadence: the answer carries `poll_after_ms`, computed from how hot the match actually is. One algorithm, owned here, so sixty clients throttle themselves and the server keeps a valve it can turn.

Where your bee stands, what it is carrying, and when it may move again.

Matches forming or running, and how many seats are left in each hive.

What every settled match paid, and to whom. Free on purpose. A claim about where the money went that costs money to check is not a claim anybody should believe. Sorted and paged by the SERVER. This is the one table that grows without bound — a row per settled match, kept when everything else about the match is purged — so sending all of it and cutting it up in the browser has an end date. `t

What this service is and how to play it, in prose. The same text the website serves at ``/llms.txt`` — one file, published on both surfaces, because an agent that arrives through the MCP door should not have to go and scrape the front door to find out where it is. It is the front-door answer to a problem the web app cannot solve on its own: a single-page app hands a fetcher an empty mount div,

Ask the hives to advance now rather than at the next tick. Carries no authority: it can only cause work that was already due — start a match whose grace has run out, or end one whose ceiling has fallen.

Buy a drone a seat in the next match. Seats fill the fullest hive that still has room, so a match reaches its quorum and starts rather than leaving everyone waiting in five thin hives.

Move one cell through open air or an open tunnel.

Cut one fresh cell of comb — slower than flying, and open to everyone after.

Bring down an open tunnel cell, so the bees behind you must cut it again. Costs one move and a fare, and sets a rival back several — a bee has a body, so a bee stuck behind a seal is also a wall for everyone behind it.

Take the winner's share as credit, or send it on to the charity.

Operator: open, close and settle matches. `restricted`, so the runtime requires the caller to be the operator, proven. This is the cron entry point; `check_now` is the same work without authority.

Who the charity share goes to, and where to check them. Free on purpose. A claim about where somebody's money goes that costs money to verify is not a claim anybody should have to take on trust.

Operator: what the wallet can send, and what is owed out of it. `restricted`, so the runtime requires the caller to be the operator, proven. `sendable_sats` is the local end of the node's channels — the only balance a Lightning payment can draw on. `owed_sats` is what this service's own settlements say is still to go out, computed from its own tables. `node_reachable: false` means the balance

Operator: send a settled match's charity or winner share over Lightning. `restricted`, so the runtime requires the caller to be the operator, proven. This is the only tool here that moves real sats, and the only one whose effect cannot be undone by writing another row. The amount is READ from the settlement, never recomputed, so a payment can never be for a figure the ledger does not already car

Operator: pay everything owed to the charity, in one Lightning payment. `restricted`, so the runtime requires the caller to be the operator, proven. The charity share accrues match by match and settles as a batch, which is the shape this always needed: a single match's share can be smaller than the fee floor it would cost to route, so paying per match can cost more than it delivers. Every unpai

Every payment attempted, and how it went. Free on purpose. A service that says 80% of every pot goes to a charity should let anybody check that sats actually left, not merely that a row was written saying they were owed. Failures are listed too — a payout history that only shows successes is a claim, not a record.

Operator: name the beneficiary, its website and its Lightning address. `restricted`, so the runtime requires the caller to be the operator, proven. It was a constant in the source, which made changing who the money goes to a deployment. A charity can be replaced, renamed, or rotate its wallet, and none of that should need anybody to touch code. Changing this never rewrites history: every settle

What you have said should happen to your winnings. `set` is False for a patron who has never said — which still reads as `donate`, because that is the default, but lets a screen show the difference between a choice made and a choice never faced.

Say now what should happen if you win. Decided BEFORE the round, deliberately. Asking in the moment is asking somebody to make a decision about money with a trophy on the screen, and a winner who has never thought about it should still end the round with their share settled rather than owed. Donating is the default. Keeping it needs somewhere to send it, so a patron who turns donation off withou

Three honey sellers near a place, each with an address and a website. Four directories hold a corner of the answer each — the USDA's local-food listings, OpenStreetMap, Google Places and sellers' own Nostr listings — so this asks all four at once, merges what agrees, checks that each website still answers and ranks by evidence, completeness, agreement and distance. `sources` says who answered