# Lonniev Tollbooth Authority Newengland MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.lonniev%2Ftollbooth-authority-newengland
Registry id: `mcp-registry/io.github.lonniev/tollbooth-authority-newengland`
Status: auth-required (checked 2026-10-27T01:24:44.282Z)

## Verdict

Lonniev Tollbooth Authority Newengland MCP server answered 99.93% of Glimind's liveness checks over 30 days, better than 31% of MCP servers, with 2726 ms median handshake and 3 outages in 90 days. Its agent-readiness grade is A (91/100) across 70 tools, costing an agent about 15,256 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.93% | 31% of MCP servers |
| Median handshake latency | 2726 ms | 1% of MCP servers |
| p95 handshake latency | 6001 ms | — |
| Checks in 30 days | 2,859 | — |
| Outages, 90 days | 3 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 91/100 (A) | 71% of MCP servers |
| Tools | 70 | — |
| Tool-list size for an agent | ~15,256 tokens | 13% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "lonniev-tollbooth-authority-newengland-m": {
      "type": "http",
      "url": "https://tollbooth-authority-newengland.fastmcp.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http lonniev-tollbooth-authority-newengland-m https://tollbooth-authority-newengland.fastmcp.app/mcp
```

## Tools (70)

- `authority_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 dail
- `authority_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
- `authority_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 / a
- `authority_approve_adoption`: Approve a pending request and provision the operator. The deferred-courtship counterpart to register_operator: same ``authority_proof`` consent, same provisioni
- `authority_audit_bootstrap_configs`: Audit every operator's bootstrap config on the relays, and republish what needs it. Republishes a config when fewer than three relays hold it, or when it was la
- `authority_certify_credits`: Certify a purchase order: return a Schnorr-signed Nostr event certificate. The paid_tool decorator handles the ad valorem fee debit and stores the cost in runti
- `authority_check_authority_approval`: Step 3/3 of Authority onboarding — check parent approval, activate Authority.
- `authority_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 to
- `authority_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 t
- `authority_check_dpyc_membership`: Look up an npub in the DPYC community registry.
- `authority_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 req
- `authority_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.
- `authority_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 
- `authority_confirm_authority_claim`: Step 2/3 of Authority onboarding — verify candidate DM, escalate to parent Authority. The parent Authority is resolved from THIS Authority's own entry in dpyc-c
- `authority_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
- `authority_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 t
- `authority_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 — t
- `authority_deregister_operator`: Remove an Operator from the DPYC community registry. Requires the same two proofs as ``register_operator``: - ``proof`` proves the caller controls the Operator'
- `authority_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 l
- `authority_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 np
- `authority_get_adoption_status`: Read an operator's adoption-request status (free, no proof). Status (pending/approved/rejected/provisioned) isn't sensitive — it's the operator's own request — 
- `authority_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, d
- `authority_get_notarization_proof`: Generate a Merkle inclusion proof that a patron's balance was included in a Bitcoin-notarized snapshot.
- `authority_get_operator_config`: Retrieve operator bootstrap configuration (Neon URL, schema). Gated by Schnorr signature proving ownership of the requested npub.
- `authority_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 patr
- `authority_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 w
- `authority_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 m
- `authority_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
- `authority_list_adoption_requests`: Owner queue: list pending operator-adoption requests. Restricted to the Authority owner (consent proof). This is the review-on-your-own-time surface the Pricing
- `authority_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 th
- `authority_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 u
- `authority_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
- `authority_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_close
- `authority_list_neon_alerts`: Owner queue: operators that reported a Neon-402 (store locked). Restricted to the Authority owner. A companion to network_persistence_health: this is the reacti
- `authority_list_notarizations`: List recent Bitcoin notarization records.
- `authority_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 c
- `authority_network_persistence_health`: Owner view: the health of the DPYC economy's accounting store (Neon). Restricted to the Authority owner. Three layers, from most to least proactive: 1. ``projec
- `authority_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 hour
- `authority_operator_status`: View registration status, balance summary, and the Authority's Nostr npub. When an explicit ``npub`` is provided, requires a Schnorr proof of ownership — withou
- `authority_oracle_about`: Describe the DPYC ecosystem via the Oracle. Free.
- `authority_oracle_get_tax_rate`: Get the current DPYC certification tax rate. Free.
- `authority_oracle_how_to_join`: Get DPYC onboarding instructions from the Oracle. Free.
- `authority_oracle_lookup_member`: Look up a DPYC community member by npub. Free.
- `authority_oracle_network_advisory`: Get active network advisories from the Oracle. Free.
- `authority_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'
- `authority_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
- `authority_receive_adoption_request`: Inbound: record an operator's request to be adopted by this Authority. Called MCP-to-MCP by the operator's ``request_adoption``. Verifies the operator controls 
- `authority_receive_credentials`: Pick up credentials from the Secure Courier. Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is ``receive_npub_proof``). **Call this onl
- `authority_receive_neon_402_alert`: Inbound: an operator reports its Neon store is 402-locked. Called MCP-to-MCP by the operator's runtime the instant it catches a Neon HTTP 402 on its own databas
- `authority_receive_npub_proof`: Receive npub ownership confirmation from a patron. Completes the npub-OWNERSHIP-PROOF flow (the credential-delivery counterpart is ``receive_credentials``). **C
- `authority_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-pat
- `authority_register_authority_npub`: Step 1/3 of Authority onboarding — send a Nostr DM challenge to the candidate.
- `authority_register_operator`: Provision an operator in the Authority ledger. Creates a ledger entry so the operator can purchase credits and certify purchase orders. Idempotent — safe to cal
- `authority_reject_adoption`: Reject a pending operator-adoption request (owner consent).
- `authority_repair_operator_schema`: 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 
- `authority_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 too
- `authority_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. Resolv
- `authority_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
- `authority_request_echo`: 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 fi
- `authority_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 ca
- `authority_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 sat
- `authority_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 manua
- `authority_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
- `authority_service_status`: Check the health and configuration of this service. Free.
- `authority_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 v
- `authority_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.
- `authority_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`` o
- `authority_update_operator`: Update an existing Operator's community registry entry. Requires the same two proofs as ``register_operator``: - ``proof`` proves the caller controls the Operat
- `authority_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-deli
- `authority_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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.