Tollbooth Authority Newengland

io.github.lonnievPublished by GitHub account lonnievv0.6.0Updated Oct 24, 2026

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

The publisher's own server: authority.md

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote New England sub-regional certification Authority in the DPYC tollbooth federation, letting an assistant handle authority claims and approvals over OAut

What you can do
Handle Authority onboarding: confirm an authority claim and check approval status, with approvals escalated to the NorthAmerica parent Authority rather than Prime. Rely on shared wheel-resident Authority tools for certification, signing, replay tracking and tenant provisioning, whose catalog is documented in the canonical Authority README. Operate as one link in a three-deep certification chain (Prime, NorthAmerica, NewEngland) for operators serving New England patrons.
When to use it
Relevant if you are an operator or participant in the DPYC tollbooth ecosystem who wants certification and approval handled through the New England sub-regional Authority, keeping latency and audit trails local. Most users outside that ecosystem will find little to do with it.
Requirements
A remote MCP endpoint reached over streamable HTTP at the published service address, with OAuth authentication required. The server side needs its own operator key and a pooled Neon database connection; those are operator deployment secrets, not client settings.
Before you install
OAuth sign-in is required before use. The README describes payment infrastructure and a fee cascade, so certification may involve monetary transactions; confirm costs before proceeding. Onboarding actions submit claims and trigger approval messages to a parent Authority, so they change state in the federation.

Installation

In SourceWeft

  1. Open Tollbooth Authority Newengland in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lonniev%2Ftollbooth-authority-newengland/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

Tollbooth Authority New England

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

The New England exit off the North American on-ramp.

Identity: npub157hmysd6sw7m8kkldycnnc74mssxp9nweddk2p5sw9l2nktr950qyxrenn Parent: tollbooth-authority-northamerica (npub1zummm…xd2t) Service: https://tollbooth-authority-newengland.fastmcp.app/mcp Neon region: aws-us-east-2 (Ohio)

A sub-regional Authority certified by NorthAmerica. The first 3-deep Authority chain in the DPYC ecosystem (Prime → NorthAmerica → NewEngland); operators serving New England patrons may choose NE to keep certification latency and audit trails as local as the protocol allows.

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 Authority @tool definitions are wheel-resident and shared with every other Authority MCP in the ecosystem.

NE was scaffolded from tollbooth-authority at the start (May 16, 2026) but is no longer a fork — wheel v0.22.0 collapsed every shared module into tollbooth.authority.*. The two repos now coexist as independent thin consumers of the same mixin, distinct only in identity, region, and Neon tenant.

For protocol semantics, certificate format, fee cascade, and tool catalog, see the canonical tollbooth-authority README.

Onboarding chain note

NE's onboarding (confirm_authority_claim → check_authority_approval) escalates to NorthAmerica, not Prime — the wheel's resolve_my_parent_npub reads NE's own upstream_authority_npub from the dpyc-community registry and routes the approval DM there. The 3-deep chain is transparent to the protocol; the registry is the source of truth.

Deploy

Two secrets required by Horizon:

Env varValue
TOLLBOOTH_NOSTR_OPERATOR_NSECNE's nsec
NEON_DATABASE_URLA pooled Neon connection string in aws-us-east-2

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

DPYC Ecosystem

NE is one Authority in the wider DPYC federation — a Social Contract of Operators and Authorities bound by transparent, auditable economic rules, with a Certification Chain cascading from the First Curator down through regional Authorities like this one.

License

Apache-2.0

Source: README.md at commit b90575f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.6.0LatestOct 21, 2026
  2. v0.5.9Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Authority integrations