io.github.lonniev/tollbooth-oauth2-collector
REMOTE · TOLLBOOTH-OAUTH2-COLLECTOR.FASTMCP.APP
Unauthenticated OAuth2 callback collector for Tollbooth MCP services
Available components
Last scanned (23 minutes ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 679 tokens (~169/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Tool “store_code” rewrote its description, which is the text the model reads security
- “retrieve_code” reworded the description of “state” cosmetic
- “store_code” reworded the description of “state” cosmetic
- 2 Nov 26 0
- Server version: 4.1.4 → 4.1.5 functional
- 29 Oct 26 0
- Server version: 4.1.3 → 4.1.4 functional
- 26 Oct 26 0
- Server version: 4.1.1 → 4.1.3 functional
- 19 Oct 26 0
- Server version: 4.1.0 → 4.1.1 functional
- 18 Oct 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 3.4.7 → 4.1.0 functional
- Tool “collector_status” changed its title: Collector Status cosmetic
- Tool “retrieve_code” changed its title: Retrieve Code cosmetic
- Tool “service_status” changed its title: Service Status cosmetic
- Tool “store_code” changed its title: Store Code cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://tollbooth-oauth2-collector.fastmcp.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fastmcp.app | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 17 Jun 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | a1583bafd89c7b58780ef1a0a0d2ad7 |
| SANs: *.fastmcp.app | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tollbooth-oauth2-collector.fastmcp.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| fastmcp.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tollbooth-oauth2-collector.fastmcp.app/mcp | Verified | 200 | |
| http (plaintext) | http://tollbooth-oauth2-collector.fastmcp.app/mcp | HTTPS enforced | 301 | https://tollbooth-oauth2-collector.fastmcp.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
collector_status Collector Status ~21
Health check — shows the number of pending authorization codes and TTL.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
retrieve_code Retrieve Code ~93
Retrieve a stored authorization code (one-time read, auto-deleted). Called by the originating MCP server to pick up the code after the user has authorized in the browser. Returns the encrypted code which the caller decrypts using the same state token.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Where the code was filed: patron npub + the flow's secret (the SDK's ``oauth_code_key`` of the authorization state). |
Structured output declared, but exposes no named fields.
No examples provided.
service_status Service Status ~172
Report the running build so a redeploy can be verified. Free. Delegates to the SDK's canonical ``build_service_status`` — the single source of the service_status payload shape — so this collector reports the same envelope as every other DPYC service. The load-bearing field is ``build_info.fastmcp_cloud_git_commit_sha``: the commit Horizon actually deployed. The post-merge deploy-verify probe reads it to confirm the live service redeployed the merged sha; with no ``service_status`` tool to probe, that sha reads as ``<none>`` and an otherwise-healthy deploy is flagged as "did not land". The vault/courier/operator fields are ``False``/empty by construction — this is an unauthenticated community utility with no operator runtime.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
store_code Store Code ~190
Store a sealed OAuth2 authorization code. Called by the serverless callback function after the browser redirect. The ``state`` carries the patron npub, the operator npub (the PUBLIC key the code is sealed to) and the flow's one-time secret — see the SDK's ``pack_oauth_state``. The code is sealed with NIP-44 to the operator so only that operator's nsec can open it. The Neon row is keyed by ``oauth_code_key(state)`` (patron npub + secret), so only the flow that holds the secret finds it: a link someone else built with a patron's npub files its code where that patron's flow never looks.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The authorization code from the OAuth provider. |
| state | string | yes | The packed state (``patron_npub.operator_npub.secret``). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.lonniev/tollbooth-oauth2-collector MCP server?
io.github.lonniev/tollbooth-oauth2-collector is a hosted endpoint at https://tollbooth-oauth2-collector.fastmcp.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tollbooth-oauth2-collector.fastmcp.app
claude mcp add --transport http lonniev-tollbooth-oauth2-collector 'https://tollbooth-oauth2-collector.fastmcp.app/mcp'
What is the io.github.lonniev/tollbooth-oauth2-collector MCP server?
io.github.lonniev/tollbooth-oauth2-collector is an MCP server listed in the public MCP registry as io.github.lonniev/tollbooth-oauth2-collector. Unauthenticated OAuth2 callback collector for Tollbooth MCP services. This page covers its hosted endpoint (https://tollbooth-oauth2-collector.fastmcp.app/mcp).
Is the io.github.lonniev/tollbooth-oauth2-collector MCP server safe to use?
io.github.lonniev/tollbooth-oauth2-collector scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.lonniev/tollbooth-oauth2-collector MCP server expose?
io.github.lonniev/tollbooth-oauth2-collector exposes 4 tools: store_code, retrieve_code, collector_status, service_status. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the io.github.lonniev/tollbooth-oauth2-collector MCP server require authentication?
No. We connected to io.github.lonniev/tollbooth-oauth2-collector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.lonniev/tollbooth-oauth2-collector MCP server still maintained?
io.github.lonniev/tollbooth-oauth2-collector is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.