# io.github.lonniev/tollbooth-authority-newengland (remote · tollbooth-authority-newengland.fastmcp.app)

Tollbooth Authority New England — sub-regional certifier under North America

- Trust score: 61/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `tollbooth-authority-newengland.fastmcp.app`: 61/100 (this document), [markdown](https://verifymcp.io/servers/lonniev-tollbooth-authority-newengland/tollbooth-authority-newengland.md), [page](https://verifymcp.io/servers/lonniev-tollbooth-authority-newengland/tollbooth-authority-newengland)

## Channel facts

- Endpoint: `https://tollbooth-authority-newengland.fastmcp.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 66 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 50/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 10079 tokens (~152/item across 66 items; 66 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 72% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.lonniev-tollbooth-authority-newengland]
url = "https://tollbooth-authority-newengland.fastmcp.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lonniev-tollbooth-authority-newengland": {
      "type": "remote",
      "url": "https://tollbooth-authority-newengland.fastmcp.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lonniev-tollbooth-authority-newengland --url https://tollbooth-authority-newengland.fastmcp.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lonniev-tollbooth-authority-newengland:
    url: "https://tollbooth-authority-newengland.fastmcp.app/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (66)

### `authority_check_balance` (~208 tokens)

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.

Input parameters:

- `dpop_token` (string, required): 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, required): The Nostr public key (npub1...) whose balance to check.

### `authority_purchase_credits` (~198 tokens)

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.

Input parameters:

- `amount_sats` (integer): Satoshis to purchase (default 1000).
- `dpop_token` (string, required): 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, required): The Nostr public key (npub1...) the credits will fund.

### `authority_check_payment` (~194 tokens)

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.

Input parameters:

- `dpop_token` (string, required): 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…
- `invoice_id` (string, required): The invoice ID returned by purchase_credits.
- `npub` (string, required): The Nostr public key (npub1...) that purchased the invoice.

### `authority_restore_credits` (~233 tokens)

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.

Input parameters:

- `dpop_token` (string, required): A kind-27235 Nostr event signed by the OPERATOR's nsec for this tool. Patron proofs are rejected.
- `invoice_id` (string, required): The BTCPay invoice ID to verify and credit.
- `patron_npub` (string, required): The patron's npub whose ledger receives the grant.

### `authority_account_statement` (~222 tokens)

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.

Input parameters:

- `days` (integer): Number of days of daily usage history to include (default 30).
- `dpop_token` (string, required): 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, required): The patron's Nostr public key (npub1...).

### `authority_account_statement_infographic` (~222 tokens)

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.

Input parameters:

- `days` (integer): Number of days of daily usage history to include (default 30).
- `dpop_token` (string, required): 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, required): The Nostr public key (npub1...) whose statement to render.

### `authority_report_issue` (~347 tokens)

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.

Input parameters:

- `body` (string, required): The details — which tool, what was wrong, what you expected.
- `dpop_token` (string, required): 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, required): Your Nostr public key (npub1...); the report's author of record.
- `title` (string, required): One-line summary of the problem.
- `tool_name` (string): Optional: the specific tool the report is about (e.g. "schwab_get_option_chain").

### `authority_service_status` (~20 tokens)

Check the health and configuration of this service. Free.

### `authority_get_operator_onboarding_status` (~56 tokens)

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.

### `authority_get_patron_onboarding_status` (~137 tokens)

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.

Input parameters:

- `dpop_token` (string, required): A kind-27235 Nostr event signed by patron_npub for this tool.
- `patron_npub` (string, required): The patron's Nostr public key (npub1...).

### `authority_session_status` (~285 tokens)

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.

Input parameters:

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

### `authority_request_credential_channel` (~250 tokens)

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.

Input parameters:

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

### `authority_receive_credentials` (~322 tokens)

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.

Input parameters:

- `credential_card` (string): Optional. An ncred1... card to redeem directly (bypasses the relay drain; dpop_token not needed).
- `dpop_token` (string): Required. The session phrase returned by request_credential_channel for this exact channel.
- `sender_npub` (string): Required. The npub that sent the credentials.
- `service` (string): Required. The credential service name (must match the service used in request_credential_channel).

### `authority_forget_credentials` (~195 tokens)

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.

Input parameters:

- `dpop_token` (string, required): 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, required): The Nostr public key (npub1...) whose credentials to forget.
- `service` (string, required): The credential service to forget.

### `authority_update_patron_credential` (~217 tokens)

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.

Input parameters:

- `dpop_token` (string, required): 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, required): The credential field name to set.
- `npub` (string, required): The patron's Nostr public key (npub1...).
- `value` (string, required): The value to store.

### `authority_delete_patron_credential` (~184 tokens)

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.

Input parameters:

- `dpop_token` (string, required): 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, required): The credential field name to remove.
- `npub` (string, required): The patron's Nostr public key (npub1...).

### `authority_get_patron_credential_fields` (~233 tokens)

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

Input parameters:

- `dpop_token` (string, required): 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, required): The patron's Nostr public key (npub1...).

### `authority_request_npub_proof` (~487 tokens)

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.

Input parameters:

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

### `authority_receive_npub_proof` (~309 tokens)

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.

Input parameters:

- `dpop_token` (string): Required. The dpop_token returned by request_npub_proof.
- `patron_npub` (string): Required. The patron's npub to receive proof from.

### `authority_check_proof_status` (~137 tokens)

Check whether a previously-cached dpop_token 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.

Free, no side effects — does not evict the cache or touch relays.

Input parameters:

- `dpop_token` (string): Required. The dpop_token phrase returned by ``request_npub_proof`` / ``receive_npub_proof``.
- `patron_npub` (string): Required. The patron's npub (npub1...).

### `authority_oracle_how_to_join` (~24 tokens)

Get DPYC onboarding instructions from the Oracle. Free.

### `authority_oracle_get_tax_rate` (~23 tokens)

Get the current DPYC certification tax rate. Free.

### `authority_oracle_lookup_member` (~32 tokens)

Look up a DPYC community member by npub. Free.

Input parameters:

- `npub` (string, required)

### `authority_oracle_about` (~21 tokens)

Describe the DPYC ecosystem via the Oracle. Free.

### `authority_oracle_network_advisory` (~24 tokens)

Get active network advisories from the Oracle. Free.

### `authority_check_authority_balance` (~72 tokens)

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.

### `authority_get_pricing_model` (~50 tokens)

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.

### `authority_set_pricing_model` (~67 tokens)

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.

Input parameters:

- `dpop_token` (string)
- `model_json` (string, required)

### `authority_reset_pricing_model` (~80 tokens)

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

Input parameters:

- `dpop_token` (string)

### `authority_request_adoption` (~192 tokens)

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.

Input parameters:

- `authority_npub` (string, required): 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).

### `authority_adoption_status` (~69 tokens)

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

Input parameters:

- `authority_npub` (string, required)
- `dpop_token` (string)

### `authority_restore_neon_schema` (~147 tokens)

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

Input parameters:

- `dpop_token` (string)

### `authority_list_canonical_identities` (~124 tokens)

Return canonical (tool_id, mcp_name, …) for every registered tool.

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.

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.

Free, no side effects.

### `authority_get_nostr_profile` (~87 tokens)

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.

Input parameters:

- `npub` (string)

### `authority_publish_nostr_profile` (~149 tokens)

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.

Input parameters:

- `npub` (string): The patron's Nostr public key the event must be signed by.
- `signed_event` (string): A JSON-encoded, client-signed kind-0 event.

### `authority_check_price` (~179 tokens)

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.

Input parameters:

- `dpop_token` (string)
- `npub` (string)
- `tool_id` (string, required): Either the tool's UUID (from the pricing model) or a bare capability string (e.g. ``"deal_scenario"``). FE callers usually have the capability name; this resolves both so the FE doesn't need to deriv…
- `tool_kwargs` (string): Optional JSON object with tool call parameters for ad valorem / categorical-multiplier pricing preview (e.g. '{"amount_sats": 5000}' or '{"difficulty": "sovereign", "mode": "live"}').

### `authority_list_constraint_types` (~50 tokens)

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.

### `authority_mint_coupon` (~151 tokens)

Create a new operator-owned discount coupon.

Input parameters:

- `discount_percent` (number, required): Percentage off the base price (0-100).
- `dpop_token` (string)
- `name` (string, required): The catchy code patrons type to redeem (operator-scoped uniqueness).
- `total_uses`: Aggregate cap across all patrons (default None = unlimited).
- `uses_per_patron`: How many tool calls one patron can claim the discount on (default 1; pass null/None for unlimited within the window).
- `valid_from` (string, required): ISO-8601 datetime when the coupon becomes active.
- `valid_until` (string, required): ISO-8601 datetime when the coupon expires.

### `authority_list_coupons` (~70 tokens)

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.

Input parameters:

- `dpop_token` (string)

### `authority_update_coupon` (~166 tokens)

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.

Input parameters:

- `clear_total_uses` (boolean)
- `clear_uses_per_patron` (boolean)
- `coupon_id` (string, required)
- `discount_percent`
- `dpop_token` (string)
- `name`
- `total_uses`
- `uses_per_patron`
- `valid_from`
- `valid_until`

### `authority_delete_coupon` (~81 tokens)

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.

Input parameters:

- `coupon_id` (string, required)
- `dpop_token` (string)

### `authority_redeem_coupon` (~133 tokens)

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.

Input parameters:

- `code` (string, required)
- `dpop_token` (string)
- `npub` (string, required)

### `authority_list_my_coupons` (~88 tokens)

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

Input parameters:

- `dpop_token` (string)
- `npub` (string, required)

### `authority_forget_coupon` (~87 tokens)

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

Input parameters:

- `coupon_id` (string, required)
- `dpop_token` (string)
- `npub` (string, required)

### `authority_notarize_ledger` (~53 tokens)

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.

### `authority_get_notarization_proof` (~69 tokens)

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

Input parameters:

- `notarization_id` (string, required): The notarization record ID.
- `npub` (string, required): The patron's Nostr public key (npub1...).

### `authority_list_notarizations` (~51 tokens)

List recent Bitcoin notarization records.

Input parameters:

- `limit` (integer): Maximum records to return (default 20).
- `status` (string): Optional filter (e.g., 'submitted', 'confirmed').

### `authority_register_operator` (~382 tokens)

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.

Input parameters:

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

### `authority_update_operator` (~192 tokens)

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.

Input parameters:

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

### `authority_deregister_operator` (~165 tokens)

Remove an Operator from the DPYC community registry.

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 removal. Without the Authority proof, anyone who knew an
  Operator's public npub and held its nsec could remove themselves
  from this Authority's roster without the Authority noticing.

Input parameters:

- `authority_proof` (string): Identity proof signed by the Authority's OWN npub — the Authority's consent to remove this Operator from the community registry under its signature.
- `dpop_token` (string)
- `npub` (string): Nostr npub of the Operator to deregister.

### `authority_get_operator_config` (~61 tokens)

Retrieve operator bootstrap configuration (Neon URL, schema).

Gated by Schnorr signature proving ownership of the requested npub.

Input parameters:

- `dpop_token` (string)
- `npub` (string): Your Nostr npub (bech32).

### `authority_operator_status` (~121 tokens)

View registration status, balance summary, and the Authority's Nostr npub.

When an explicit ``npub`` is provided, requires a Schnorr proof of
ownership — without it, anyone could enumerate balances by walking
the community registry. When ``npub`` is empty, falls back to the
Authority's own operator identity and skips the proof check (self-
inspection is always allowed).

Input parameters:

- `dpop_token` (string)
- `npub` (string): Nostr public key (npub1...). Defaults to operator identity if empty.

### `authority_certify_credits` (~123 tokens)

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 runtime._last_debit_cost. No recomputation needed.

Called by operator MCP servers (not end users) when a patron purchases credits.

Input parameters:

- `amount_sats` (integer): The total purchase amount in satoshis. Must be positive.
- `dpop_token` (string)
- `npub` (string): The operator's DPYC npub (from register_operator response).

### `authority_check_dpyc_membership` (~33 tokens)

Look up an npub in the DPYC community registry.

Input parameters:

- `npub` (string, required)

### `authority_receive_adoption_request` (~175 tokens)

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 ``operator_npub`` (inline Schnorr bound to the
adoption sentinel — no relay round-trip), records a durable ``pending``
row, and fires a best-effort owner-notification DM. Does NOT provision —
provisioning waits for the owner's ``approve_adoption``.

Input parameters:

- `dpop_token` (string): Inline kind-27235 proof signed by the operator's nsec, bound to the canonical adoption sentinel. request_adoption mints this automatically.
- `operator_npub` (string): The operator's Nostr npub requesting adoption.
- `service_url` (string): The operator's MCP endpoint URL.

### `authority_list_adoption_requests` (~67 tokens)

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

Input parameters:

- `authority_proof` (string): Proof signed by the Authority's OWN npub (owner consent).

### `authority_receive_neon_402_alert` (~205 tokens)

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 database. Verifies the operator controls
\``npub`` (inline Schnorr bound to this tool's wire name), records a
durable latest-state row, and fires a best-effort owner-notification
DM. This is how the Authority learns the store is dark BEFORE a patron
files a complaint.

Input parameters:

- `detail` (string): Short, credential-free error summary (the Neon 402 message).
- `dpop_token` (string): Inline kind-27235 proof signed by the operator's nsec, bound to this tool's wire name. The operator's runtime mints and sends this automatically when it catches a Neon 402.
- `npub` (string): The reporting operator's Nostr npub (the one whose store is locked).

### `authority_list_neon_alerts` (~85 tokens)

Owner queue: operators that reported a Neon-402 (store locked).

Restricted to the Authority owner. A companion to network_persistence_health:
this is the reactive list (operators that already went dark); the health
tool adds the proactive per-project compute posture.

Input parameters:

- `authority_proof` (string): Proof signed by the Authority's OWN npub (owner consent).

### `authority_network_persistence_health` (~219 tokens)

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\. ``projects`` — if a Neon API key is configured (NEON_API_KEY), the
   per-project compute-quota posture across the org: hours used, %,
   reset date, and a status ladder (ok/warning/critical/exhausted) so a
   project can be topped up BEFORE it 402s. ``configured=false`` when no
   key is present (deliver one to enable the proactive watch).
2\. ``own_store`` — reactive self-detection: whether the Authority's OWN
   database answers, or is itself 402-locked. Always available.
3\. ``operator_alerts`` — operators that reported a 402 (from
   receive_neon_402_alert). Reactive, but immediate.

Input parameters:

- `authority_proof` (string): Proof signed by the Authority's OWN npub (owner consent).

### `authority_approve_adoption` (~98 tokens)

Approve a pending request and provision the operator.

The deferred-courtship counterpart to register_operator: same
\``authority_proof`` consent, same provisioning effect
(``_provision_operator``) — just supplied later, after review.

Input parameters:

- `authority_proof` (string): Proof signed by the Authority's OWN npub (owner consent).
- `operator_npub` (string): The operator npub to approve and provision.

### `authority_reject_adoption` (~69 tokens)

Reject a pending operator-adoption request (owner consent).

Input parameters:

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

### `authority_repair_operator_schema` (~147 tokens)

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.

Input parameters:

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

### `authority_get_adoption_status` (~81 tokens)

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 — so the operator can poll it openly via
its ``adoption_status`` tool.

Input parameters:

- `operator_npub` (string): The operator npub whose request status to read.

### `authority_register_authority_npub` (~54 tokens)

Step 1/3 of Authority onboarding — send a Nostr DM challenge to the candidate.

Input parameters:

- `candidate_npub` (string, required): The Nostr npub of the candidate who wants to become the curator.

### `authority_confirm_authority_claim` (~107 tokens)

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-community: whatever its ``upstream_authority_npub`` names. For
Lonnie-Authority and NorthAmerica that's Prime; for NewEngland it's
NorthAmerica; chain depth is transparent.

Input parameters:

- `candidate_npub` (string, required): The Nostr npub of the candidate who replied to the DM challenge.

### `authority_check_authority_approval` (~49 tokens)

Step 3/3 of Authority onboarding — check parent approval, activate Authority.

Input parameters:

- `candidate_npub` (string, required): The Nostr npub of the candidate awaiting parent Authority approval.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lonniev-tollbooth-authority-newengland/tollbooth-authority-newengland#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://tollbooth-authority-newengland.fastmcp.app/mcp
- Repository: https://github.com/lonniev/tollbooth-authority-newengland
- Changelog RSS feed: https://verifymcp.io/servers/lonniev-tollbooth-authority-newengland/tollbooth-authority-newengland/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lonniev-tollbooth-authority-newengland/tollbooth-authority-newengland/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lonniev-tollbooth-authority-newengland/tollbooth-authority-newengland