Tollbooth Authority Newengland

io.github.lonnievv0.5.9更新於 Oct 4, 2026

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

已驗證Streamable HTTP可網頁執行Security & MonitoringBusiness & Commerce

概覽

AI 產生的概覽

面向 DPYC 收費亭聯邦新英格蘭次區域的遠端認證機構端點，負責營運者入駐與審批。

功能
這是一個輕量遠端 MCP 端點，在 DPYC 生態系中扮演次區域 Authority。它提供入駐與認證相關的 Authority 工具，包括 confirm_authority_claim 與 check_authority_approval，審批會向上級 Authority（NorthAmerica）升級。入駐狀態機、簽署器、重放追蹤與租戶開通等共用邏輯位於 tollbooth-dpyc 套件中，而非本儲存庫。
適用情境
適用於在 DPYC 聯邦中服務新英格蘭使用者、並希望在協定允許範圍內盡量本地化認證延遲與稽核紀錄的營運者。它不是面向一般助理任務的通用工具。
執行需求
遠端 streamable HTTP 端點；清單未宣告任何套件、環境變數或標頭。README 說明了服務本身的部署期密鑰：TOLLBOOTH_NOSTR_OPERATOR_NSEC 與 NEON_DATABASE_URL，以及部署後交付的 BTCPay 憑證。
安裝前請注意
README 列出了服務使用的密鑰，包括 TOLLBOOTH_NOSTR_OPERATOR_NSEC（Nostr 私鑰）與 NEON_DATABASE_URL，並提到收銀用的 BTCPay 憑證。入駐涉及審批流程與經濟規則；請將任何簽署金鑰或付款憑證視為敏感資訊，並在使用前確認端點。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Tollbooth Authority Newengland，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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

來源：README.md，提交 b90575f

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.5.9最新Sep 16, 2026