io.github.lonniev/tollbooth-authority
REMOTE · TOLLBOOTH-AUTHORITY.FASTMCP.APP · SCANNED SEP 20
Tollbooth Authority — Certified Purchase Order Service for DPYC operators
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 68 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 10752 tokens (~158/item across 68 items; 68 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "authority_forget_credentials" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 69 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.lonniev/tollbooth-authority MCP server?
io.github.lonniev/tollbooth-authority is a hosted endpoint at https://tollbooth-authority.fastmcp.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tollbooth-authority.fastmcp.app
claude mcp add --transport http lonniev-tollbooth-authority 'https://tollbooth-authority.fastmcp.app/mcp'
{
"mcpServers": {
"lonniev-tollbooth-authority": {
"url": "https://tollbooth-authority.fastmcp.app/mcp"
}
}
} {
"servers": {
"lonniev-tollbooth-authority": {
"type": "http",
"url": "https://tollbooth-authority.fastmcp.app/mcp"
}
}
} [mcp_servers.lonniev-tollbooth-authority] url = "https://tollbooth-authority.fastmcp.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lonniev-tollbooth-authority": {
"type": "remote",
"url": "https://tollbooth-authority.fastmcp.app/mcp",
"enabled": true
}
}
} openclaw mcp add lonniev-tollbooth-authority --url 'https://tollbooth-authority.fastmcp.app/mcp' --transport streamable-http
mcp_servers:
lonniev-tollbooth-authority:
url: "https://tollbooth-authority.fastmcp.app/mcp" {
"McpServers": {
"lonniev-tollbooth-authority": {
"Transport": "http",
"Url": "https://tollbooth-authority.fastmcp.app/mcp"
}
}
} assistant mcp add lonniev-tollbooth-authority -t streamable-http -u 'https://tollbooth-authority.fastmcp.app/mcp'
{
"mcpServers": {
"lonniev-tollbooth-authority": {
"type": "http",
"url": "https://tollbooth-authority.fastmcp.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Aug 26 +1
- Tool “authority_account_statement” rewrote its description, which is the text the model reads security
- Tool “authority_account_statement_infographic” rewrote its description, which is the text the model reads security
- Tool “authority_check_balance” rewrote its description, which is the text the model reads security
- Tool “authority_check_payment” rewrote its description, which is the text the model reads security
- Tool “authority_check_price” rewrote its description, which is the text the model reads security
- Tool “authority_check_proof_status” rewrote its description, which is the text the model reads security
- Tool “authority_delete_operator_credential” rewrote its description, which is the text the model reads security
- Tool “authority_delete_patron_credential” rewrote its description, which is the text the model reads security
- Tool “authority_forget_credentials” rewrote its description, which is the text the model reads security
- Tool “authority_get_notarization_proof” rewrote its description, which is the text the model reads security
- Tool “authority_get_patron_credential_fields” rewrote its description, which is the text the model reads security
- Tool “authority_get_patron_onboarding_status” rewrote its description, which is the text the model reads security
- Tool “authority_list_notarizations” rewrote its description, which is the text the model reads security
- Tool “authority_mint_coupon” rewrote its description, which is the text the model reads security
- Tool “authority_publish_nostr_profile” rewrote its description, which is the text the model reads security
- Tool “authority_purchase_credits” rewrote its description, which is the text the model reads security
- Tool “authority_receive_credentials” rewrote its description, which is the text the model reads security
- Tool “authority_receive_npub_proof” rewrote its description, which is the text the model reads security
- Tool “authority_report_issue” rewrote its description, which is the text the model reads security
- Tool “authority_request_adoption” rewrote its description, which is the text the model reads security
- Tool “authority_request_credential_channel” rewrote its description, which is the text the model reads security
- Tool “authority_request_npub_proof” rewrote its description, which is the text the model reads security
- Tool “authority_restore_credits” rewrote its description, which is the text the model reads security
- Tool “authority_session_status” rewrote its description, which is the text the model reads security
- Tool “authority_update_operator_credential” rewrote its description, which is the text the model reads security
- Tool “authority_update_patron_credential” rewrote its description, which is the text the model reads security
- Tool coverage: 23% → 73% ▲ functional
- Server version: 3.2.3 → 3.4.7 functional
- “authority_account_statement” reworded the description of “days” cosmetic
- “authority_account_statement” reworded the description of “dpop_token” cosmetic
- “authority_account_statement” reworded the description of “npub” cosmetic
- “authority_account_statement_infographic” reworded the description of “days” cosmetic
- “authority_account_statement_infographic” reworded the description of “dpop_token” cosmetic
- “authority_account_statement_infographic” reworded the description of “npub” cosmetic
- “authority_check_balance” reworded the description of “dpop_token” cosmetic
- “authority_check_balance” reworded the description of “npub” cosmetic
- “authority_check_payment” reworded the description of “dpop_token” cosmetic
- “authority_check_payment” reworded the description of “invoice_id” cosmetic
- “authority_check_payment” reworded the description of “npub” cosmetic
- “authority_check_price” reworded the description of “tool_id” cosmetic
- “authority_check_price” reworded the description of “tool_kwargs” cosmetic
- “authority_check_proof_status” reworded the description of “dpop_token” cosmetic
- “authority_check_proof_status” reworded the description of “patron_npub” cosmetic
- “authority_delete_operator_credential” reworded the description of “dpop_token” cosmetic
- “authority_delete_operator_credential” reworded the description of “field” cosmetic
- “authority_delete_patron_credential” reworded the description of “dpop_token” cosmetic
- “authority_delete_patron_credential” reworded the description of “field” cosmetic
- “authority_delete_patron_credential” reworded the description of “npub” cosmetic
- “authority_forget_credentials” reworded the description of “dpop_token” cosmetic
- “authority_forget_credentials” reworded the description of “npub” cosmetic
- “authority_forget_credentials” reworded the description of “service” cosmetic
- “authority_get_notarization_proof” reworded the description of “notarization_id” cosmetic
- “authority_get_notarization_proof” reworded the description of “npub” cosmetic
- “authority_get_patron_credential_fields” reworded the description of “dpop_token” cosmetic
- “authority_get_patron_credential_fields” reworded the description of “npub” cosmetic
- “authority_get_patron_onboarding_status” reworded the description of “dpop_token” cosmetic
- “authority_get_patron_onboarding_status” reworded the description of “patron_npub” cosmetic
- “authority_list_notarizations” reworded the description of “limit” cosmetic
- “authority_list_notarizations” reworded the description of “status” cosmetic
- “authority_mint_coupon” reworded the description of “discount_percent” cosmetic
- “authority_mint_coupon” reworded the description of “name” cosmetic
- “authority_mint_coupon” reworded the description of “total_uses” cosmetic
- “authority_mint_coupon” reworded the description of “uses_per_patron” cosmetic
- “authority_mint_coupon” reworded the description of “valid_from” cosmetic
- “authority_mint_coupon” reworded the description of “valid_until” cosmetic
- “authority_publish_nostr_profile” reworded the description of “npub” cosmetic
- “authority_publish_nostr_profile” reworded the description of “signed_event” cosmetic
- “authority_purchase_credits” reworded the description of “amount_sats” cosmetic
- “authority_purchase_credits” reworded the description of “dpop_token” cosmetic
- “authority_purchase_credits” reworded the description of “npub” cosmetic
- “authority_receive_credentials” reworded the description of “credential_card” cosmetic
- “authority_receive_credentials” reworded the description of “dpop_token” cosmetic
- “authority_receive_credentials” reworded the description of “sender_npub” cosmetic
- “authority_receive_credentials” reworded the description of “service” cosmetic
- “authority_receive_npub_proof” reworded the description of “dpop_token” cosmetic
- “authority_receive_npub_proof” reworded the description of “patron_npub” cosmetic
- “authority_report_issue” reworded the description of “body” cosmetic
- “authority_report_issue” reworded the description of “dpop_token” cosmetic
- “authority_report_issue” reworded the description of “npub” cosmetic
- “authority_report_issue” reworded the description of “title” cosmetic
- “authority_report_issue” reworded the description of “tool_name” cosmetic
- “authority_request_adoption” reworded the description of “authority_npub” cosmetic
- “authority_request_adoption” reworded the description of “dpop_token” cosmetic
- “authority_request_adoption” reworded the description of “note” cosmetic
- “authority_request_adoption” reworded the description of “service_url” cosmetic
- “authority_request_credential_channel” reworded the description of “sender_npub” cosmetic
- “authority_request_credential_channel” reworded the description of “service” cosmetic
- “authority_request_npub_proof” reworded the description of “patron_npub” cosmetic
- “authority_request_npub_proof” reworded the description of “reason” cosmetic
- “authority_request_npub_proof” reworded the description of “verify_at” cosmetic
- “authority_restore_credits” reworded the description of “dpop_token” cosmetic
- “authority_restore_credits” reworded the description of “invoice_id” cosmetic
- “authority_restore_credits” reworded the description of “patron_npub” cosmetic
- “authority_session_status” reworded the description of “patron_npub” cosmetic
- “authority_update_operator_credential” reworded the description of “dpop_token” cosmetic
- “authority_update_operator_credential” reworded the description of “field” cosmetic
- “authority_update_operator_credential” reworded the description of “value” cosmetic
- “authority_update_patron_credential” reworded the description of “dpop_token” cosmetic
- “authority_update_patron_credential” reworded the description of “field” cosmetic
- “authority_update_patron_credential” reworded the description of “npub” cosmetic
- “authority_update_patron_credential” reworded the description of “value” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- New tool “authority_delete_operator_credential” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Schema quality: good → fair functional
- New tool “authority_update_operator_credential” functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://tollbooth-authority.fastmcp.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fastmcp.app | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 17 Jun 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | a1583bafd89c7b58780ef1a0a0d2ad7 |
| SANs: *.fastmcp.app | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tollbooth-authority.fastmcp.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| fastmcp.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tollbooth-authority.fastmcp.app/mcp | Verified | 200 | |
| http (plaintext) | http://tollbooth-authority.fastmcp.app/mcp | HTTPS enforced | 301 | https://tollbooth-authority.fastmcp.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authority_register_authority_npub ~54
Step 1/3 of Authority onboarding — send a Nostr DM challenge to the candidate.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_npub | string | yes | The Nostr npub of the candidate who wants to become the curator. |
Structured output declared, but exposes no named fields.
No examples provided.
authority_register_operator ~382
Provision an operator in the Authority ledger. Creates a ledger entry so the operator can purchase credits and certify purchase orders. Idempotent — safe to call again. Requires TWO independent identity proofs: 1. ``proof`` — Schnorr proof signed by the candidate operator's ``npub``. Proves the requester really controls that npub. The operator typically calls ``request_npub_proof`` / ``receive_npub_proof`` against this Authority first to mint a cached dpop_token. 2. ``authority_proof`` — Schnorr proof signed by the Authority's own npub. This is the Authority's human consent — only an agent with the Authority's nsec on hand can produce it. Apps generate this inline when the human admin clicks 'adopt'; otherwise an Authority-side proof can be minted the same way an operator-side one is. Next step: Call purchase_credits to fund your credit balance.
| Name | Type | Req | Description |
|---|---|---|---|
| authority_proof | string | – | Identity proof signed by the Authority's OWN npub — the Authority's discretionary consent to adopt this Operator. Apps with the Authority's nsec in their keystore (e.g. the Pricing Studio) produce th… |
| display_name | string | – | Human-readable name for the Operator service, shown in the community roster (e.g. 'my-service'). If empty, the roster falls back to a truncated npub. |
| dpop_token | string | – | – |
| npub | string | – | Your Nostr npub (bech32). Get one from the dpyc-oracle's how_to_join() tool. |
| service_url | string | – | Your MCP endpoint URL (e.g. 'https://my-service.fastmcp.app/mcp'). |
Structured output declared, but exposes no named fields.
No examples provided.
authority_reject_adoption ~69
Reject a pending operator-adoption request (owner consent).
| Name | Type | Req | Description |
|---|---|---|---|
| authority_proof | string | – | Proof signed by the Authority's OWN npub (owner consent). |
| operator_npub | string | – | The operator npub to reject. |
| reason | string | – | Optional human-readable reason. |
Structured output declared, but exposes no named fields.
No examples provided.
authority_repair_operator_schema ~147
Owner repair: reassign every table in an operator's tenant schema to the operator's own role, then re-grant DML. For tenants whose tables were created/owned by the provisioning role — the operator role then cannot CREATE INDEX on them ("must be owner"), which aborts the whole vault bootstrap. Unlike register_operator this does NOT rotate the operator's DB password or re-send the bootstrap DM; it only fixes ownership + grants in place. Idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| authority_proof | string | – | Proof signed by the Authority's OWN npub (owner consent). |
| operator_npub | string | – | The operator npub whose tenant-schema ownership to repair. |
Structured output declared, but exposes no named fields.
No examples provided.
authority_report_issue ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The details — which tool, what was wrong, what you expected. |
| dpop_token | string | yes | Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… |
| npub | string | yes | Your Nostr public key (npub1...); the report's author of record. |
| title | string | yes | One-line summary of the problem. |
| tool_name | string | – | Optional: the specific tool the report is about (e.g. "schwab_get_option_chain"). |
Structured output declared, but exposes no named fields.
No examples provided.
authority_request_adoption ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authority_npub | string | yes | npub of the Authority to request adoption from. |
| dpop_token | string | – | operator-npub ownership proof (inline kind-27235 or cached token). |
| note | string | – | optional message for the Authority owner. |
| service_url | string | – | this operator's MCP endpoint (advertised to the Authority). |
Structured output declared, but exposes no named fields.
No examples provided.
authority_request_credential_channel ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sender_npub | string | – | Required. The npub to send the template to. |
| service | string | – | Required. The credential service name (e.g., from get_operator_onboarding_status or get_patron_onboarding_status). |
Structured output declared, but exposes no named fields.
No examples provided.
authority_request_npub_proof ~487
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.
| Name | Type | Req | Description |
|---|---|---|---|
| patron_npub | string | – | Required. The patron's npub to request proof from. |
| reason | string | – | Optional. A human-readable purpose for the request ("I'm working on your request XYZ and need the Operator to do ABC for you"). Signed into the provenance attestation and shown in the DM, so the reci… |
| verify_at | string | – | Optional. A free-form statement of WHERE you (the initiating agent) already showed this proof's one-time code to the user — a URL, or "your Claude.ai conversation", "the Grok session". The OAuth 2.0… |
Structured output declared, but exposes no named fields.
No examples provided.
authority_reset_pricing_model ~80
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).
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
authority_restore_credits ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | yes | A kind-27235 Nostr event signed by the OPERATOR's nsec for this tool. Patron proofs are rejected. |
| invoice_id | string | yes | The BTCPay invoice ID to verify and credit. |
| patron_npub | string | yes | The patron's npub whose ledger receives the grant. |
Structured output declared, but exposes no named fields.
No examples provided.
authority_restore_neon_schema ~147
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).
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
authority_service_status ~20
Check the health and configuration of this service. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
authority_session_status ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| patron_npub | string | – | Optional. If supplied, the response includes an ``upstream_oauth`` block with the patron's stored OAuth token expiry (runtime-derived from vault state) so a client can refresh proactively rather than… |
Structured output declared, but exposes no named fields.
No examples provided.
authority_set_pricing_model ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | – | – |
| model_json | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
authority_update_coupon ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clear_total_uses | boolean | – | – |
| clear_uses_per_patron | boolean | – | – |
| coupon_id | string | yes | – |
| discount_percent | – | – | – |
| dpop_token | string | – | – |
| name | – | – | – |
| total_uses | – | – | – |
| uses_per_patron | – | – | – |
| valid_from | – | – | – |
| valid_until | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
authority_update_operator ~192
Update an existing Operator's community registry entry. Requires the same two proofs as ``register_operator``: - ``proof`` proves the caller controls the Operator's ``npub``. - ``authority_proof`` proves the Authority's human admin consents to the change. Without the Authority proof, anyone with the Operator's nsec could redirect their own ``service_url`` under this Authority's signature without the Authority's awareness.
| Name | Type | Req | Description |
|---|---|---|---|
| authority_proof | string | – | Identity proof signed by the Authority's OWN npub — the Authority's consent to modify this Operator's registry entry. |
| display_name | string | – | New display name (leave empty to keep current). |
| dpop_token | string | – | – |
| npub | string | – | Nostr npub of the Operator to update. |
| service_url | string | – | New MCP endpoint URL (leave empty to keep current). |
Structured output declared, but exposes no named fields.
No examples provided.
authority_update_operator_credential ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | yes | Operator proof for this tool. |
| field | string | yes | The operator credential field to set. Must be declared in the operator's credential template. |
| value | string | yes | The value to store. |
Structured output declared, but exposes no named fields.
No examples provided.
authority_update_patron_credential ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dpop_token | string | yes | Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… |
| field | string | yes | The credential field name to set. |
| npub | string | yes | The patron's Nostr public key (npub1...). |
| value | string | yes | The value to store. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.lonniev/tollbooth-authority MCP server?
io.github.lonniev/tollbooth-authority is an MCP server listed in the public MCP registry as io.github.lonniev/tollbooth-authority. Tollbooth Authority, Certified Purchase Order Service for DPYC operators. This page covers its hosted endpoint (https://tollbooth-authority.fastmcp.app/mcp).
Is the io.github.lonniev/tollbooth-authority MCP server safe to use?
io.github.lonniev/tollbooth-authority scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.lonniev/tollbooth-authority MCP server expose?
io.github.lonniev/tollbooth-authority exposes 68 tools: authority_check_balance, authority_purchase_credits, authority_check_payment, authority_restore_credits, authority_account_statement, and 63 more. Their descriptions and schemas cost roughly 9,760 tokens of context every time the server is loaded.
Does the io.github.lonniev/tollbooth-authority MCP server require authentication?
No. We connected to io.github.lonniev/tollbooth-authority without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.lonniev/tollbooth-authority MCP server still maintained?
io.github.lonniev/tollbooth-authority is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.