mcp-registry/io.github.lonniev/tollbooth-oauth2-collector · v4.1.1
As of 2026-10-23 02:53 UTC, the Lonniev Tollbooth Oauth2 Collector MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Unauthenticated OAuth2 callback collector for Tollbooth MCP services
Claude Code
claude mcp add --transport http lonniev-tollbooth-oauth2-collector-mcp-s https://tollbooth-oauth2-collector.fastmcp.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"lonniev-tollbooth-oauth2-collector-mcp-s": {
"type": "http",
"url": "https://tollbooth-oauth2-collector.fastmcp.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,946 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lonniev%2Ftollbooth-oauth2-collector/fixes
{
"name": "collector_status",
"description": "Health check — shows the number of pending authorization codes and TTL.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Collector Status"
}{
"name": "retrieve_code",
"description": "Retrieve a stored authorization code (one-time read, auto-deleted).\n\nCalled by the originating MCP server to pick up the code after the user\nhas authorized in the browser. Returns the encrypted code which the\ncaller decrypts using the same state token.",
"inputSchema": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"description": "The state token (patron npub) used during authorization."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Retrieve Code"
}{
"name": "service_status",
"description": "Report the running build so a redeploy can be verified. Free.\n\nDelegates to the SDK's canonical ``build_service_status`` — the single\nsource of the service_status payload shape — so this collector reports the\nsame envelope as every other DPYC service. The load-bearing field is\n``build_info.fastmcp_cloud_git_commit_sha``: the commit Horizon actually\ndeployed. The post-merge deploy-verify probe reads it to confirm the live\nservice redeployed the merged sha; with no ``service_status`` tool to probe",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Service Status"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lonniev/tollbooth-oauth2-collector"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.lonniev/tollbooth-oauth2-collector"}) over MCP.
store_code ~225 tokensservice_status ~174 tokensretrieve_code ~137 tokenscollector_status ~54 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.lonniev%2Ftollbooth-oauth2-collector?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lonniev%2Ftollbooth-oauth2-collector?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lonniev%2Ftollbooth-oauth2-collector.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lonniev%2Ftollbooth-oauth2-collector.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.lonniev%2Ftollbooth-oauth2-collector?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3ccc819503af6f69…, first seen 2026-10-17, included at leaf 19095 of 49,595. Version history · verify what your client received.
Compare: most reliable other servers · most reliable security servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 02:53 UTC, the Lonniev Tollbooth Oauth2 Collector MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Lonniev Tollbooth Oauth2 Collector MCP server advertises 4 tools, including collector_status, retrieve_code, service_status, store_code.
Point your MCP client at this streamable-http endpoint: https://tollbooth-oauth2-collector.fastmcp.app/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.