mcpField
T
tollbooth-authority-northamerica

tollbooth-authority-northamerica

Remote
github.com/lonnievFinance0Updated today
Repository

About tollbooth-authority-northamerica

tollbooth-authority-northamerica is a regional certifier for DPYC operators in North America, operating under the DPYC Prime Authority. It shares the common Authority implementation and has a New England sub-authority.

Key features

  1. 01Regional operator certification
  2. 02DPYC Prime as its parent Authority
  3. 03New England sub-authority support
  4. 04Shared tollbooth-dpyc Authority tools
  5. 05Neon tenant in the Oregon region

Use cases

  1. 01Certifying operators serving North America
  2. 02Using a regional Authority for certification
  3. 03Maintaining certification records in the regional Neon tenant

MCP support

Exposes the shared Tollbooth Authority tools to MCP clients through a FastMCP server. The server uses the common tollbooth-dpyc Authority extension.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://tollbooth-authority-northamerica.fastmcp.app/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

70
ParameterTypeRequiredDescription
npubstringYesThe Nostr public key (npub1...) whose balance to check.
dpop_tokenstringYesProof that the caller holds npub: the grant envelope from receive_npub_proof, or the raw JSON of a kind-27235 Nostr event signed by npub whose `u` tag is this tool's name.

Details

From the project README

Tollbooth Authority — North America

Milo drives the Lightning Turnpike — Don't Pester Your Customer

The North American on-ramp to the Lightning turnpike.

Identity: npub1zummm5awn88kw2hz6deeyjprpw0fzuv9rvzrxf3vu453yyqzvdss49xd2t Parent: DPYC Prime Authority (npub1l94pd…mq8pf) Peer Authorities under Prime: tollbooth-authority (Lonnie-Authority) Sub-Authority: tollbooth-authority-newengland Service: https://tollbooth-authority-northamerica.fastmcp.app/mcp Neon region: aws-us-west-2 (Oregon)

A peer-level Authority under DPYC Prime, serving North American operators. Operators may choose this Authority to keep certification latency and audit trails in-region.

The metaphors in this project are drawn with admiration from The Phantom Tollbooth by Norton Juster, illustrated by Jules Feiffer (1961). We just built the payment infrastructure.


Architecture

This repository is a thin consumer of the tollbooth-dpyc wheel's tollbooth.authority extension (wheel ≥ 0.22.1). The entire deployable surface lives in src/tollbooth_authority/server.py (~90 lines): a FastMCP instance, an OperatorRuntime, and two register_*_tools(mcp, runtime) calls. Onboarding state machine, Schnorr signer, replay tracker, Neon tenant provisioning, and the 16 Authority @tool definitions are wheel-resident and shared with every other Authority MCP in the ecosystem.

For the protocol semantics, certificate format (Schnorr/NIP-33 kind 30079), fee cascade, registry enforcement, and tool catalog, see the canonical tollbooth-authority README — this repo is identical in behavior, distinct only in identity, region, and Neon tenant.

Deploy

Two secrets required by Horizon:

Env varValue
TOLLBOOTH_NOSTR_OPERATOR_NSECThis Authority's nsec
NEON_DATABASE_URLA pooled Neon connection string in aws-us-west-2

Everything else — BTCPay credentials for the cashier, operator credential templates — arrives via Secure Courier post-deploy (see docs/how-to-add-authority.md in the community repo).

The DPYC Ecosystem

DPYC is a federation of independent, SSE-based MCP servers sharing one Lightning-funded economy. This Authority certifies operators across the network. Sibling repos:

Core & governance

Operators (paid MCP services)

Utilities & advocates

License

Apache-2.0

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.