tollbooth-oauth2-collector
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Tollbooth OAuth2 Collector
An unauthenticated "dumb mailbox" FastMCP server that holds OAuth2 authorization codes for retrieval by the originating MCP server. A companion serverless function (Val Town) receives the browser redirect from the OAuth provider and hands the code to this collector's store_code MCP tool. This two-part design works around Horizon proxying only POST traffic on the /mcp/ path — browser GET redirects from OAuth providers cannot reach @mcp.custom_route endpoints, so a serverless callback bridges the gap.
How It Works
┌───────────────┐ 1. redirect_uri → serverless ┌──────────────────────┐
│ OAuth Provider│ ─────────────────────────────────→│ Serverless callback │
│ (e.g. Schwab) │ GET ?code=AUTH_CODE&state=STATE │ (Val Town) │
└───────────────┘ └──────────────────────┘
│
2. POST store_code │
(JSON-RPC /mcp/) ▼
┌──────────────────────┐
│ OAuth2 Collector │
│ store_code tool │
│ → seals + Postgres │
└──────────────────────┘
│
│ 3. code stored
▼
┌──────────────┐ 4. retrieve_code(state=PATRON) ┌──────────────────────┐
│ MCP Server │ ─────────────────────────────────→ │ OAuth2 Collector │
│ (e.g. │ (JSON-RPC /mcp/) │ retrieve_code tool │
│ schwab-mcp) │ ←───────────────────────────────── │ → returns code once │
└──────────────┘ {"found": true, "code": ...} │ → deletes from DB │
└──────────────────────┘MCP server starts an OAuth flow, setting
redirect_urito the serverless callback function's URL. Itsstateis<patron npub>.<operator npub>(the SDK'spack_oauth_state)User authorizes in the browser; the OAuth provider redirects to the serverless callback with
?code=...&state=...Serverless callback (Val Town) POSTs the code to the collector's
store_codeMCP tool over/mcp/Collector seals the code to the operator npub with NIP-44 (the SDK's
encrypt_collector_code) and stores it in Postgres under the patron npub (600s TTL)MCP server calls the
retrieve_code(state=<patron npub>)MCP tool to pick up the sealed code (one-time read, auto-deleted)MCP server opens the seal with its own nsec (
decrypt_collector_code) and exchanges the code for a token using its own credentials
The collector also exposes collector_status (pending-code count and TTL) and service_status (deployed build, incl. git sha) as free MCP tools. The serverless callback source lives in val/oauth_callback.js. A change to it on main deploys it to Val Town (.github/workflows/deploy-val-town.yml, which needs the VALTOWN_TOKEN secret).
Related MCP server: MCP Credentials Broker
Deployment
Deploy to Horizon:
fastmcp deploy server.pySet the NEON_DATABASE_URL environment variable in Horizon to point to your Neon Postgres instance.
DPYC Advocate Identity
This collector is registered as an Advocate in the DPYC Social Contract. Consuming MCP servers discover its URL by asking the Oracle:
from tollbooth.oracle_client import default_oracle_client
svc = await default_oracle_client().resolve_service(name="tollbooth-oauth2-collector")
collector_url = svc["url"] # e.g., "https://tollbooth-oauth2-collector.fastmcp.app"No OAUTH_COLLECTOR_URL env var needed — peer discovery is handled by the registry.
Register the serverless callback function's URL (not the collector's) in your OAuth provider's developer portal. It is registered separately in the DPYC registry under the name tollbooth-oauth2-callback, and the SDK's begin_oauth uses it as the redirect_uri:
callback = await default_oracle_client().resolve_service(name="tollbooth-oauth2-callback")
redirect_uri = callback["url"] # e.g., "https://tollbooth-dpyc-oauth.val.run"Security Model
Auth codes are useless alone — exchanging a code requires
client_id+client_secret, held only by the consuming MCP serverSealed at rest — codes are sealed with NIP-44 to the operator npub carried in the state (the SDK's
encrypt_collector_code); only that operator's nsec opens them, and the state is never a keyPublic state — the state carries only two npubs, public keys that are safe to route through the browser; a state with no operator npub is refused
One-time read — codes are deleted immediately after retrieval (prevents replay)
Short TTL — expired codes are automatically cleaned up (600s)
No secrets stored — the collector never sees client credentials or tokens
Related Repositories
Repository | Description |
Python SDK for Tollbooth monetization | |
DPYC Social Contract registry and governance | |
Free community concierge — membership, governance, onboarding | |
Certification Authority MCP service | |
Reference Operator implementation / template | |
iOS pricing editor for Operators | |
Monetized graph answers — named Cypher over Neo4j/AuraDB | |
Schwab brokerage MCP server | |
Personal Brain knowledge-graph MCP server | |
X (Twitter) posting MCP server | |
Tax sorting and classification MCP server | |
Options analytics MCP server | |
Region-scoped farm climate analytics MCP server | |
The Bee's Knees multiplayer race MCP server | |
Roastify coffee catalog and packaging artwork MCP server | |
Desktop chart relay MCP server | |
Shared browser SDK for operator front ends | |
OAuth2 callback collector (Advocate) | |
URL shortener utility (Advocate) |
License
Copyright 2026 Lonnie VanZandt. Licensed under the Apache License, Version 2.0.
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Create and manage CodeQR short links, QR codes, and analytics from any MCP client.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA complete OAuth 2.1 server implementation for FastMCP with PKCE support, enabling secure authentication and authorization flows. Provides authorization code exchange, token management, and refresh capabilities for building authenticated MCP applications.-
- AlicenseAqualityDmaintenanceProvides secure OAuth2-based credential management for MCP servers, allowing agents to obtain short-lived token references without exposing raw secrets.712 npmMIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server framework for single-owner production deployments using OAuth authorization code flow with PKCE, providing endpoints for MCP, authorization, token, and metadata.-
- AlicenseNot gradedqualityAmaintenanceEnables you to publish remote MCP tools from your own Lambda behind a single HTTP API endpoint, with selectable authorization (IAM, API key, JWT, Lambda, or Google Workspace), stage throttling, JSON access logs, and RFC 9728 resource metadata discovery. No session table or sticky routing is needed, so any invocation can answer any request.19 npmMIT