Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Tollbooth Authority — North America Certify my operator for the Lightning network"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The North American on-ramp to the Lightning turnpike.
Identity:
npub1zummm5awn88kw2hz6deeyjprpw0fzuv9rvzrxf3vu453yyqzvdss49xd2tParent: DPYC Prime Authority (npub1l94pd…mq8pf) Peer Authorities under Prime:tollbooth-authority(Lonnie-Authority) Sub-Authority:tollbooth-authority-newenglandService:https://tollbooth-authority-northamerica.fastmcp.app/mcpNeon 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.
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.
Related MCP server: lightning-mcp
Two secrets required by Horizon:
Env var | Value |
| This Authority's nsec |
| A pooled Neon connection string in |
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).
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
tollbooth-dpyc — shared Python SDK (crypto, vault, auth, pricing, audit)
dpyc-community — governance registry (members, rulebook, CI validation)
dpyc-oracle — free community concierge (membership, onboarding, tax-rate questions)
tollbooth-authority — canonical certification Authority
tollbooth-sample — reference Operator implementation
tollbooth-pricing-studio — native pricing editor (Swift/iOS)
Operators (paid MCP services)
cypher-mcp — monetized graph answers via named Cypher templates over Neo4j/AuraDB (certified under this Authority)
schwab-mcp — Charles Schwab brokerage data
thebrain-mcp — TheBrain knowledge-graph access
excalibur-mcp — X/Twitter posting
taxsort-mcp — tax classification + Cloudflare Pages UI
optionality-mcp — options analytics
Utilities & advocates
tollbooth-oauth2-collector — shared OAuth2 callback collector
tollbooth-shortlinks — URL shortener
Apache-2.0
This server cannot be deployed
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
AI governance MCP server for EU AI Act compliance and jurisdiction verification
Hosted MCP server for AI agent identity, permissions, verification, and reusable proof.
Official MCP server for Certifier to issue, manage, and track certificates and badges.
