io.github.lonniev/excalibur-mcp

Post a tweet with a hero banner image to X/Twitter. Provide either an image_url (fetched and attached) or banner_svg (rendered to PNG and attached). Text supports the same markdown formatting as post_tweet.

Launch a publisher for every due post (operator-only). Selects ``scheduled`` posts whose ``publish_at`` has arrived, claims each atomically, and starts one background publisher per post. It does NOT publish: composing content, billing the owner, posting to X and recording the outcome all belong to the publisher, which runs on the async job queue and so may take the minutes a dynamic block needs. This call returns as soon as the work is dispatched — expect it to be fast even when the publishing itself is slow, and read per-post outcomes from ``get_scheduler_log`` or the post rows. Requires the operator's npub proof; the trigger itself is free. Returns ``{kind: "tick", processed, launched, contended}``.

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.

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.

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.

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 the ``dpop_token`` — the same token. The calling application MUST remember it and pass it as the ``dpop_token`` parameter on every subsequent paid tool call. The proof (a hash of the token) is stored in the vault keyed by that hash — the MCP never stores the raw token itself. Free.

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.

Refine a flagged region of a post with an LLM — server-side. The operator's LLM key stays in the vault and never leaves the server. Send the flagged ``region``, the surrounding ``full_text``, an optional ``instruction`` (what to change), and the editor's ``voice`` profile + ``bans`` (JSON array or comma list of banned constructions). Returns ``{"success": true, "suggestions": [...3 strings...]}``. Paid: the AI cost is metered as a tollbooth fare. The fare is refunded if no LLM key is configured or the upstream call returns nothing.

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.

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.

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.

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 demonstrated-proof-of-possession token that the calling application MUST remember and pass as the ``dpop_token`` parameter on every subsequent paid tool call. The MCP does not retain this value across restarts. **Lifecycle:** The cached proof expires after the patron's chosen duration. When it expires, call ``request_npub_proof`` again for a fresh challenge, then wait for the user, then call ``receive_npub_proof``. Free.

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

Start resolving a dynamic post block with an LLM — returns a CLAIM CHECK. A dynamic block's ``prompt`` is run by the model (with web search + web fetch for live data) and woven into the surrounding post ``context`` in the author's ``voice``. The author's instruction governs length — there is no character cap (X supports long-form posts). The operator's LLM key stays in the vault and never leaves the server. Because that work (paginated fetches + generation) can outlast a client timeout, this returns immediately with a **claim check** instead of the text: ``{"success": true, "claim_check": "...", "status": "pending", "poll_after_seconds": N}``. Redeem it with the free companion ``fetch_dynamic_block(claim_check)`` until ``status == "done"`` (then read ``result.text``). (The scheduler resolves blocks directly server-side at fire time and does not use this tool.) Paid: the AI cost is metered as a tollbooth fare on THIS start call, refunded if no LLM key is configured or the job ultimately fails.

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.

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 successful re-run is harmless. Returns the per-step result. If any step raises, surfaces the Neon error message inline (0.31.0 reads the SQL error body that earlier wheels swallowed behind ``raise_for_status``). RESTRICTED to operator — requires proof (nsec-signed).

Save a reusable post snippet (opening/footer/CTA). Omit ``snippet_id`` to create a new one; pass it to update an existing snippet in place (name/text/ favorite/doc). On update only the fields you pass change — omit ``favorite`` (leave it null) to keep it as-is, so a doc-only patch (e.g. toggling a snippet dynamic) doesn't reset it. ``doc`` is the same block/flag document a post carries, so the editor is identical for both. Free and owner-scoped. Returns ``{"success": true, "snippet": …}``.

Save your writing Voice (replaces the previous one — it is a per-npub singleton). ``profile`` is free text. ``bans`` is a list of ``{text, on}`` objects: ``text`` is the construction to avoid, ``on`` whether it is an active constraint. Blank/duplicate entries are dropped server-side. Owner-scoped; priced by the operator's pricing model (use ``check_price``). Returns ``{"success": true, "voice": {...}}``.

Ask the scheduler to run one tick now (free; any proven patron). Pokes the Worker's ``/tick`` — the same work the ~30-minute cron does: it claims a pending proof reply (completing the operator's authorization) and fires any due posts. Use it right after the operator approves in Studio so nobody waits for the next tick. Deliberately NOT operator-only. Approving is the operator's act; noticing that they approved is anyone's, and a patron watching a parked scheduler is often the one who notices first. The poke carries no authority — it cannot approve anything, only ask the Worker to look. The challenge phrase stays operator-gated (``scheduler_pending``). The Worker runs the tick in the background and returns immediately; re-read ``scheduler_status`` a few seconds later to see the phase flip. Returns ``{started: true}`` or ``{started: false}`` if the Worker couldn't be reached.

What is the scheduled-post cron Worker waiting on? (operator-only). When the Worker's authorization lapses it DMs the operator a challenge phrase and parks. This returns that pending phrase so the operator can match it against the DM before approving in Studio — the Device-Grant second surface for a headless actor. The phrase lives only in the Worker's KV (an impostor can't inject it); we read it AS the operator (a kind-27235 signed with the operator key), so the human never signs anything in the browser. ``restricted``: gated to the operator npub, free. Never returns the active session token. Returns ``{phase, code, reason, requestedAt}`` — ``phase`` is ``pending`` / ``active`` / ``idle``, or ``unavailable`` if the Worker can't be reached.

Send the scheduler's proof request again, now (operator-only). For a pending request that is not going to complete — the reply went to an older DM, or ``scheduler_pending`` shows a last check that says the request was replaced or expired. The Worker drops it and DMs a fresh one straight away instead of waiting out its hour. Approve the NEWEST DM in Studio, then ``scheduler_check_now``. Signed as the operator with a sentinel ``u``-tag the Worker checks literally, like ``scheduler_pending``, so the browser signs nothing. An already-authorized scheduler is left alone. ``restricted``: gated to the operator npub, free. Returns ``{success, phase, requestedAt, message}``.

The scheduler's configuration and current status (free; any proven patron). Relays the cron Worker's public ``/status`` — cadence, version, renewal window, and current authorization phase (``pending`` / ``active`` / ``idle``, no challenge phrase) — and adds the operator npub it acts for. No secrets: the pending phrase (operator-only) is ``scheduler_pending``; the per-tick traffic log is ``get_scheduler_log``. Returns the merged config, or ``{worker: "unavailable"}`` merged in if the Worker can't be reached.

Check the health and configuration of this service. Free.

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 tool call — it will warm up on demand. - 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_registered: Operator has no Authority relationship yet. Call register_operator first. - no_identity: Operator nsec is not configured. Deployment issue.

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.

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.

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.

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.

Patch a stored post. ``patch`` may set ``doc, publish_at, recurrence, cease_at, status`` (omit a field to leave it unchanged). ``text_cache`` is written when supplied (alongside a doc change). ``client_req_id`` dedupes debounced autosave retries — a repeat is a no-op with no second charge.