World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Tollbooth Authority — Certified Purchase Order Service for DPYC operators
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Tollbooth Authority。按照 https://mcp.popnx.com/i/lonniev-tollbooth-authority.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(tollbooth-authority.fastmcp.app) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Tollbooth Authorityhttps://tollbooth-authority.fastmcp.app/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsTollbooth Authority
用 Tollbooth Authority 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Tollbooth Authority,或回答中出现 Tollbooth Authority 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Tollbooth Authorityhttps://tollbooth-authority.fastmcp.app/mcp开启新聊天,输入前先从插件列表中选择 Tollbooth Authority
用 Tollbooth Authority 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Tollbooth Authority,或回答中出现 Tollbooth Authority 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user tollbooth-authority https://tollbooth-authority.fastmcp.app/mcp应能看到 Tollbooth Authority 在列表中并显示已连接
用 Tollbooth Authority 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Tollbooth Authority,或回答中出现 Tollbooth Authority 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Tollbooth Authority 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Tollbooth Authority,或回答中出现 Tollbooth Authority 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Tollbooth Authority 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Tollbooth Authority,或回答中出现 Tollbooth Authority 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://tollbooth-authority.fastmcp.app/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user tollbooth-authority https://tollbooth-authority.fastmcp.app/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"tollbooth-authority": {
"url": "https://tollbooth-authority.fastmcp.app/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"tollbooth-authority": {
"type": "http",
"url": "https://tollbooth-authority.fastmcp.app/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 lonniev 验证,该账户拥有此仓库
代码最后更新于昨天
使用 Apache-2.0
在 513 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/lonniev-tollbooth-authority)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(0.12.0)于29天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Tollbooth Authority | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The institution that built the infrastructure.
*The metaphors in this project are drawn with admiration from* The Phantom Tollbooth *by Norton Juster, illustrated by Jules Feiffer (1961). Milo, Tock, the Tollbooth, Dictionopolis, and Digitopolis are creations of Mr. Juster's extraordinary imagination. We just built the payment infrastructure.*
Every turnpike has an authority. Not the operators who run the booths, and not the drivers who pay the fares — but the institution that poured the concrete, erected the signs, and stamped the purchase orders.
The Tollbooth Authority is the Massachusetts Turnpike Authority of the Lightning economy. It doesn't operate any toll booths. It doesn't touch operator BTCPay stores. It never sees user payment data. What it does is simpler and more essential:
The Authority's signature is the proof that the turnpike is legitimate. Without the stamp, the toll booth doesn't open.
As of v0.9.0, this Authority is a thin consumer of the tollbooth-dpyc wheel. Every piece of generic Authority code — onboarding state machine, Schnorr certificate signer, replay tracker, Neon tenant provisioner, and the full Authority tool surface — lives in the wheel's tollbooth.authority package. This repo's server.py supplies only actor-specific configuration: identity name, human-readable instructions, OperatorRuntime construction, and two register_*_tools(mcp, runtime) calls.
# The entire server.py, distilled
from fastmcp import FastMCP from tollbooth.authority import ( AUTHORITY_TOOL_REGISTRY, OPERATOR_CREDENTIAL_TEMPLATE, register_authority_tools, ) from tollbooth.runtime import OperatorRuntime, register_standard_tools from tollbooth.tool_identity import STANDARD_IDENTITIES
mcp = FastMCP("tollbooth-authority", instructions="…") runtime = OperatorRuntime( tool_registry={STANDARD_IDENTITIES, AUTHORITY_TOOL_REGISTRY}, vault_source="env", # Authority arrives with its own Neon purchase_mode="auto", # derive direct/certified from the registry chain service_name="Tollbooth Authority", ots_enabled=True, operator_credential_template=OPERATOR_CREDENTIAL_TEMPLATE, ) register_standard_tools(mcp, "authority", runtime, ...) register_authority_tools(mcp, runtime)
Refactor history:
OperatorRuntime and delegated standard tools to the wheel — ~1,900 lines → ~970._verify_operator_proof helper was promoted to wheel-side tollbooth.identity_proof.require_proof.tollbooth.authority.*.@tool definitions into register_authority_tools(mcp, runtime).0.4.0 releases.The Tollbooth ecosystem is a three-party protocol spanning three repositories:
| Repo | Role |
|---|---|
| tollbooth-authority (this repo) | The institution — fee collection, Schnorr signing, purchase order certification |
| tollbooth-dpyc | The booth — operator-side credit ledger, BTCPay client, tool gating |
| thebrain-mcp | The first city — reference MCP server powered by Tollbooth |
The three-party protocol above is the core, but the Authority certifies a wider federation of independent MCP services, all built on the same tollbooth-dpyc SDK:
| Repo | Role |
|---|---|
| tollbooth-dpyc | Shared SDK — crypto, vault, auth, pricing, audit |
| dpyc-community | Governance registry — members/read-only-lookup-cache.json, GOVERNANCE.md, CI validation |
| dpyc-oracle | Free community concierge — membership, governance, onboarding answers |
| tollbooth-authority | This repo — certification backbone, Schnorr certs, fee ledger |
| tollbooth-sample | Reference template for new operators |
| tollbooth-pricing-studio | Pricing editor — native iOS, Nostr DMs |
| cypher-mcp | Monetized graph answers — named Cypher over Neo4j/AuraDB |
| schwab-mcp | Charles Schwab brokerage data |
| thebrain-mcp | TheBrain knowledge-graph access |
| excalibur-mcp | X/Twitter posting |
| taxsort-mcp | Tax sorting + classification |
| optionality-mcp | Options analytics |
| goodearth-mcp | Climate analytics for small farms |
| beesknees-mcp | The Bee's Knees race game |
| roastify-mcp | Roastify coffee catalog + packaging artwork |
| ChartRemotely-mcp | Drives a desktop chart through a paired agent |
| tollbooth-web | Shared browser SDK for operator front ends |
| tollbooth-oauth2-collector | Shared OAuth2 callback collector (community Advocate) |
| tollbooth-shortlinks | URL shortener utility |
request_adoption(authority_npub=..., service_url=..., display_name=...) on its own MCP, signing the request with its nsec. Its service delivers the request to the Authority, which records it as pending and notifies its owner. The owner approves it with approve_operator_request (or turns it down with reject_operator_request); approval creates the operator's ledger entry, provisions its isolated Neon schema and registers it through the Oracle.purchase_credits with the number of sats they want to pre-fund. The Authority returns a Lightning invoice from its own BTCPay Server. The operator pays. After settlement, check_payment credits the balance.certify_credits. The Authority deducts the 2% ad valorem fee (via the @runtime.paid_tool decorator), signs a Schnorr-based Nostr event certificate, and returns it.Certificates are Schnorr-signed Nostr events (NIP-33 parameterized replaceable events) rather than Ed25519 JWTs. Each certificate contains the operator npub in a p tag, the certified amount and protocol in t/L tags, an expiration tag, and the content field holds the structured claim data. Verification uses BIP-340 Schnorr signatures against the Authority's Nostr npub.
The Authority checks the dpyc-community registry cache members/read-only-lookup-cache.json at certification time. Operators must have "status": "active" in the registry. The registry is HTTP-cached with a configurable TTL. Design is fail-closed: if the registry is unreachable, certification is denied.
Parent Authority relationships live in the dpyc-community registry — each Authority's upstream_authority_npub points at its sponsor. Operator MCPs resolve their certifying Authority through the Oracle (resolve_authority_for(npub)), which walks that registry chain; no per-Authority env var configures the upstream. The Authority's own certify_credits simply collects the ad valorem fee from its operator's pre-funded balance and signs the certificate — no per-transaction upstream call.
certify_credits is registered as a @runtime.paid_tool with 2% ad valorem pricing on the amount_sats parameter (minimum 10 sats). The fee is debited by the decorator, and the cost is read from runtime._last_debit_cost — no double computation.
OpenTimestamps notarization is enabled (ots_enabled=True on the runtime). Ledger state can be notarized and verified through the standard notarize_ledger and get_notarization_proof tools provided by the wheel.
Every certificate includes a unique JTI (JWT ID). The Authority tracks seen JTIs in an in-memory ordered dict with TTL-based pruning. This prevents certificate replay attacks even if a certificate is intercepted before expiration.
All tools are now wheel-defined and registered by the two register_*_tools calls in server.py. For the full canonical tables (Authority tools mounted by register_authority_tools, standard tools mounted by register_standard_tools) see the tollbooth-dpyc README. The short version:
register_authority_tools(mcp, runtime). This set also includes the owner's request queue: receive_adoption_request (where an operator's adoption request arrives), list_operator_requests, approve_operator_request and reject_operator_request. The queue holds two kinds of request, an adoption and an update to an operator's registry entry (update_operator, which the operator calls and the owner approves). deregister_operator needs no approval: either the operator (leaving) or the Authority's owner (disowning it) may call it alone. repair_operator_schema is the owner's repair of a tenant's table ownership.register_standard_tools(mcp, "authority", runtime, ...).Every tool that takes npub requires the connection to prove it, and each request acts as exactly one npub. A request signed with that npub's nsec (NIP-98) proves it. A keyless client connects as an OAuth *holder* and proves the npub into its wallet once, with request_npub_proof, a reply to the DM, then receive_npub_proof. Owner-only tools require the request to prove the Authority's own npub. No proof travels in a tool argument.
The Authority runs on