A free, unauthenticated MCP concierge for the DPYC Social Contract that reads the dpyc-community registry live to answer membership, governance, onboarding, and network questions — plus a few signed registry writes.
Learn the community: about, get_rulebook, economic_model, get_tax_rate, how_to_join, how_to_add_authority, network_advisory — narration and docs straight from the repo (deliberately quotes no rates or figures, redirecting to an Authority's check_price).
Look up members: lookup_member(npub) for any role, who_is_first_curator(), check_ban_status(npub).
Discover the network: list_services(probe, kind) enumerates the live roster and optionally MCP-handshakes each endpoint for its own self-description; resolve_service(name|npub) and resolve_authority_for(npub) resolve URLs and certifying Authorities.
Relay infrastructure: get_relays() returns the curated Nostr relay set best-first; report_relay_failure(...) reports a dead relay with a signed event, and only the Oracle's own probe re-ranks it.
Version/diagnostics: network_versions() and service_status() for recommended and running component versions.
Citizenship onboarding: request_citizenship(npub, display_name) issues a challenge; confirm_citizenship(npub, challenge_id, signed_event_json) verifies a Schnorr signature and commits members/citizens/{npub}.json.
Signed registry writes (NIP-98): register_operator, update_operator, deregister_operator must be signed by the sponsoring Authority's key; register_advocate and publish_campaign must be signed by the npub they write. register_authority handles new Authority onboarding.
Pricing campaigns: publish_campaign, list_campaigns, get_campaign to share and fetch campaigns (JSON or Markdown).
Stubbed / not yet implemented: renounce_membership, initiate_ban_election, cast_ban_vote.
Allows querying membership, governance, onboarding, and tax rate data by reading the dpyc-community GitHub registry live.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@DPYC Oracle what's the current tax rate?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A free, unauthenticated MCP concierge service for the DPYC Social Contract. The Oracle answers questions about membership, governance, onboarding, and tax rates by reading the dpyc-community GitHub registry live. No credits, no Neon database, no Secure Courier, no payment or credentials required. Registry writes are the exception: each must come on a signed request (see Signed registry writes).
Tool | Params | Description |
| — | Extended narration from repo docs (README + GOVERNANCE) |
|
| Look up a member by Nostr npub |
|
| Enumerate the live service network from the registry, optionally MCP-handshaking each member for its own self-description and tool inventory |
| — | Explains per-Authority ad valorem certification taxation; quotes no rate of its own and redirects to the relevant Authority's |
| — | Qualitative model of how value flows up the Certification Chain (no hardcoded rates, counts, or revenue figures) |
| — | GOVERNANCE.md content |
| — | Tier-specific onboarding guide |
| — | End-to-end guide for spinning up a new Tollbooth Authority (fetched live from dpyc-community) |
| — | First Curator's npub and record |
| — | Current recommended component versions |
| — | Deployment advisory for operators |
| — | Runtime version diagnostics |
|
| Resolve one service by name or npub (exactly one) to its |
|
| The certifying Authority ( |
| — | The DPYC Nostr relay set from |
|
| Report a relay in the DPYC set as unreachable. The event must be signed by |
|
| Begin citizenship onboarding (issues challenge) |
|
| Complete onboarding with signed Nostr event |
|
| Register a community utility service as an Advocate; the request must be signed with |
|
| Register a new Authority (called by onboarding flow) |
|
| Register a new Operator. Called by the sponsoring Authority when its owner approves an adoption; the request must be signed with |
|
| Update an existing Operator's registry entry (e.g. new MCP endpoint). Called by the Authority when its owner approves the operator's update request; the request must be signed with |
|
| Remove an Operator from the registry, when the operator leaves its Authority or the Authority disowns it. Called by the Authority; the request must be signed with |
|
| Check if an npub is banned |
|
| Publish a pricing campaign to the DPYC community; the request must be signed with |
|
| List published pricing campaigns, optionally filtered by operator or author |
|
| Retrieve a published pricing campaign (JSON or Markdown) |
Tool | Description |
| Citizen self-removal via automated PR |
| Start economic ban voting |
| Lightning-funded ban vote |
Related MCP server: github-repos
register_operator, update_operator and deregister_operator change who the network trusts, so the Oracle takes them only from the Authority that sponsors the operator. The request must carry a NIP-98 signature (Authorization: Nostr <base64 kind-27235>, bound to the request's method, URL and body) made with the key of the authority_npub it names. An unsigned request, or one signed by any other key, is refused.
register_advocate and publish_campaign take the same NIP-98 signature, made with the key of the npub they write: an Advocate registers itself, and a campaign is published under its author's own npub. Anyone holding a key may do either; no one may do it in another npub's name.
Every other Oracle tool answers with no Authorization header at all.
Operators never call these tools themselves. An operator asks its Authority (request_adoption, update_operator or deregister_operator on the Authority), and the Authority makes the signed call here once its owner approves, or at once for a deregistration.
New citizens can self-register via Schnorr signature verification:
request_citizenship(npub, display_name) — issues a cryptographic challenge
Sign the challenge with your Nostr nsec (offline, nsec never leaves your device)
confirm_citizenship(npub, challenge_id, signed_event_json) — verifies signature and auto-commits
On success, the Oracle creates an individual member file at members/citizens/{npub}.json in dpyc-community. The CI workflow regenerates members/read-only-lookup-cache.json from the individual files.
Advocates are community utility services (e.g., OAuth2 collectors) that provide shared infrastructure but aren't monetized Operators. Registration is Oracle-mediated — no challenge-response needed:
register_advocate(
npub="<service_npub>",
display_name="My Service",
service_name="my-service",
service_url="https://my-service.fastmcp.app",
service_description="What the service does",
)The Oracle commits members/advocates/{npub}.json directly and updates members/read-only-lookup-cache.json, so the Advocate is discoverable at once. Peer MCP servers discover the service URL through this Oracle's resolve_service(name=...), which tollbooth-dpyc calls as default_oracle_client().resolve_service(name=...).
This service is hosted on Horizon. Add it to your MCP client configuration:
{
"mcpServers": {
"dpyc-oracle": {
"url": "https://dpyc-oracle.fastmcp.app/mcp"
}
}
}The authoritative, always-current roster lives in the registry — call list_services() / lookup_member() / network_versions() for live data. The stable source repos:
Core
dpyc-community — Registry, governance, and membership data
tollbooth-dpyc — Python SDK every Operator and Authority builds on
tollbooth-sample — Reference Operator template for new services
tollbooth-pricing-studio — iOS app Operators use to design pricing models
tollbooth-web — Shared browser SDK for Operator front ends
Authorities (certification chain)
tollbooth-authority — Certification + fee ledger
tollbooth-authority-northamerica — Regional certifier
tollbooth-authority-newengland — Sub-regional certifier
Operators
thebrain-mcp — Personal Brain knowledge graph
excalibur-mcp — X/Twitter posting
schwab-mcp — Charles Schwab brokerage data
taxsort-mcp — Tax sorting + classification
optionality-mcp — Options analytics
cypher-mcp — Monetized graph answers (named Cypher over Neo4j/AuraDB)
goodearth-mcp — Region-scoped farm climate analytics
beesknees-mcp — The Bee's Knees, a multiplayer race to the queen
roastify-mcp — Roastify coffee catalog and packaging artwork
ChartRemotely-mcp — Puts a security on a desktop chart through a paired agent
Advocates (shared utilities, unmonetized)
tollbooth-oauth2-collector — OAuth2 authorization-code collection
tollbooth-shortlinks — Ephemeral short URLs for OAuth flows
Apache-2.0
Extended narration about DPYC, the Social Contract, and the Oracle.
Fetches README.md and GOVERNANCE.md from the dpyc-community repo and assembles a comprehensive context answer.
Inputs: no named parameters. Returns: result
Cast a Lightning-funded vote in an active ban election.
Not yet implemented — will verify npub membership, validate the election is active, and record the vote with a Lightning payment proof.
Inputs: npub (required), vote (required), election_id (required). Returns: object
Check whether an npub is banned from the DPYC Social Contract.
Looks up the member in the community registry and checks whether their status is "banned". Unknown npubs are not considered banned (they simply aren't members).
Free, unauthenticated. Used by operators during the cold path (credit purchases) to enforce community bans.
Inputs: npub (required). Returns: object
Complete the citizen registration by submitting a signed Nostr event.
This is part of the citizen registration flow (Operator-owned). The Operator calls this on behalf of a patron after the patron has signed the cryptographic challenge from request_citizenship.
Verifies:
The challenge exists and hasn't expired
The Schnorr signature is valid
The event's pubkey matches the claimed npub
The event content contains the issued nonce
The npub is not already registered
On success, commits directly to dpyc-community/members/citizens/{npub}.json to register the new Citizen immediately.
Inputs: npub (required), challenge_id (required), signed_event_json (required). Returns: object
Remove an Operator from the DPYC community registry.
Called when an Authority disowns an Operator. An Operator cannot exist without a sponsoring Authority, so deregistration removes the member file entirely, returning the Operator to initial state.
Inputs: operator_npub (required), authority_npub (required). Returns: object
Explain the DPYC Social Contract economic model — qualitatively.
Describes how value flows through the network: ad valorem certification fees, the cascade up the Certification Chain to the First Curator, and where the live numbers actually live. The Oracle quotes no rates, counts, or revenue figures — those belong to the Authorities' pricing models and the live registry, not to a docent. Free, unauthenticated.
Inputs: no named parameters. Returns: object
Retrieve a published pricing campaign.
Inputs: slug (required), author_npub (required), operator_npub (required), format. Returns: object
Return the DPYC Nostr relay set, best first.
The single source of truth is dpyc-community/relays.json. An Operator
seeds its relay set from here at cold start (its only fixed dependency is
this Oracle endpoint), then reads its own bootstrap config from Nostr using
just its nsec — no direct GitHub access.
That file is a curated guess: it says which relays are worth using, not which are up this minute. Relays that an operator reported and the Oracle then proved unreachable are moved to the back of the list; everything else keeps its declared order, and nothing is ever dropped.
This call never probes anything — it is on every operator's cold-start
path, so it stays a lookup. Ranking improves only when someone hits a dead
relay and says so via report_relay_failure. Report failures only;
successes need no announcement.
Free.
Inputs: no named parameters. Returns: object
Fetch the DPYC Social Contract governance document.
Returns the raw markdown of GOVERNANCE.md from the dpyc-community repo.
Inputs: no named parameters. Returns: result
Explain how Tollbooth certification taxation works.
Taxation is ad valorem and per-Authority — there is no single
network-wide number, and the Oracle deliberately quotes none. The
actual fee is the Authority's own accounting, set in its pricing model
and reported at transaction time. This tool is a docent: it explains
the model and points to the live source. For the exact figure, query
the relevant Authority's check_price for certify_credits.
Inputs: no named parameters. Returns: object
End-to-end guide for spinning up a new Tollbooth Authority.
Returns the eight-step procedure covering identity, region selection, GitHub workspace, dpyc-community registry entry, Neon + BTCPay + Horizon deployment, BTCPay credential delivery via Secure Courier, the self-registration challenge-response with the parent Authority, and pre-funding the cert-fee balance. Fetched live from docs/how-to-add-authority.md in the dpyc-community repo.
Inputs: no named parameters. Returns: result
Tier-specific onboarding guide for joining the DPYC Social Contract.
Covers all five tiers: Citizen, Advocate, Operator, Authority, and First Curator. Includes Nostr keygen instructions and practical next steps.
Inputs: no named parameters. Returns: result
Initiate a community ban election against a member.
Not yet implemented — will create a GitHub Issue with a 72-hour discussion period and Lightning-funded economic voting.
Inputs: reason (required), target_npub (required). Returns: object
List published pricing campaigns from the DPYC community.
Optionally filter by operator or author npub.
Inputs: author_npub, operator_npub. Returns: object
Enumerate the live DPYC service network with self-described summaries.
Reads the member roster from the dpyc-community registry, then (when
probe=True) performs a lightweight MCP handshake against each
member's public service endpoint to fetch that service's own
self-description and tool inventory. Nothing about the services is
hardcoded here — descriptions are authored by each service, and prices
come from each Operator/Authority pricing model (call the service's
check_price).
Resilient by design: per-service timeout, partial results, brief caching, and a registry-only fallback when an endpoint is asleep or unreachable. A sleeping service never breaks the listing. Free, unauthenticated.
Inputs: kind, probe. Returns: object
Look up a member by their Nostr npub.
Can look up any role's npub — citizen, operator, or authority. Returns the full member record if found, or a not-found message.
Inputs: npub (required). Returns: result
Get current network deployment advisory.
Returns human-readable guidance on what changed recently, urgent upgrades, and actions operators should take. Fetched live from ADVISORY.md in the dpyc-community repo.
Inputs: no named parameters. Returns: result
Get current recommended versions of all Tollbooth components.
Returns component versions, minimum compatibility, active protocols, and a short advisory summary. Data is fetched live from network-status.json in the dpyc-community repo.
Inputs: no named parameters. Returns: object
Publish a pricing campaign to the DPYC community.
Commits both a machine-importable JSON file and a human-readable Markdown summary to the dpyc-community campaigns directory.
Inputs: author_npub (required), campaign_json (required), operator_npub (required), campaign_name, +1 more. Returns: object
Register a new Advocate in the DPYC community registry.
Advocates are community utility services that provide shared infrastructure (e.g., OAuth2 callback collectors) but aren't monetized Operators or certification Authorities.
This is an Oracle-mediated registration — no Nostr DM challenge-response needed. The Oracle operator (Prime Authority) trusts the commit via GitHub token.
Inputs: npub (required), service_url (required), display_name (required), service_name (required), +1 more. Returns: object
Register a new Authority in the DPYC community registry.
Called by an Authority service at the end of the onboarding protocol
(after the candidate proves npub ownership and the Prime Authority
approves). Commits a new members/authorities/{npub}.json file to
dpyc-community on GitHub.
The full Authority onboarding protocol is a 3-step Nostr DM challenge-response flow:
register_authority_npub(npub) — Authority sends DM challenge
confirm_authority_claim(npub) — verifies candidate DM, escalates to Prime
check_authority_approval(npub) — Prime approves, this tool is called
Inputs: service_url (required), display_name (required), authority_npub (required), upstream_authority_npub (required). Returns: object
Register a new Operator in the DPYC community registry.
Called by an Authority service after the operator requests registration. The Authority validates the operator's identity and sponsors the registration by calling this tool via MCP-to-MCP.
Inputs: service_url (required), display_name (required), operator_npub (required), authority_npub (required). Returns: object
Citizen self-removal from the DPYC Social Contract via automated PR.
Not yet implemented — will create a GitHub PR to remove the member from the registry.
Inputs: npub (required). Returns: object
Report that a relay in the DPYC set was unreachable, and re-rank it.
A report does not set a relay's rank. It asks the Oracle to measure that relay now, and the Oracle's own probe decides. A false or mistaken report therefore costs one probe and changes nothing — no caller can demote a healthy relay by asserting that it is down.
Report only failures. Successes are far too frequent to be worth carrying, and a relay that works needs no announcement.
Inputs: relay (required), signed_event (required), reporter_npub (required), mode. Returns: object
Begin the citizen registration process (Operator-owned flow).
This is the citizen registration path. Called by the Operator on behalf of a patron — invokes the Oracle directly. No Authority npub is required or consulted. The patron's npub is registered as a Citizen in the DPYC community.
The npub provided here becomes the user's patron identity — the keypair they will use for credit purchases and service access across all Tollbooth-monetized services.
Not to be confused with operator registration, which goes through the Authority via a Nostr DM delegation request.
Issues a cryptographic challenge that the applicant must sign with their Nostr private key (nsec) to prove they own the claimed npub. The nsec never leaves the applicant's device.
Returns a challenge_id, nonce, and signing instructions. The applicant signs a Nostr event containing the nonce and submits it via confirm_citizenship within 10 minutes.
Inputs: npub (required), display_name (required). Returns: object
Resolve the certifying Authority for an operator npub.
Returns the Authority's {npub, url, name} (from the operator's
upstream_authority_npub). Use this after bootstrap to learn — and
verify — which Authority signed your config, without reading GitHub.
Inputs: npub (required). Returns: object
Resolve a DPYC service by name or npub.
Returns {npub, url, name, role, purchase_mode} where purchase_mode
is the registry-topology fact "certified" or "direct" (not a price).
Supply exactly one of name or npub.
Inputs: name, npub. Returns: object
Diagnostic: report this service's software versions and runtime info.
Free, unauthenticated. Use to verify deployment versions across the DPYC ecosystem.
Inputs: no named parameters. Returns: object
Update an existing Operator's registry entry.
Used when an Operator moves to a new MCP endpoint, changes its display name, or needs to correct a registration. Must be called by the sponsoring Authority (or any Authority).
Inputs: operator_npub (required), service_url, display_name, authority_npub. Returns: object
Identify the First Curator (Prime Authority) of the Certification Chain.
Returns the curator's npub, display name, and member record.
Inputs: no named parameters. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 30 tools
Each tool targets a distinct resource and action—member lookups, role-specific registrations, relay management, campaigns, and informational queries are all clearly separated. Even the 'not yet implemented' ban and membership tools are unambiguous in their purpose.
The majority of tools follow a verb_noun pattern (get_rulebook, register_operator, list_campaigns), but a substantial minority use bare nouns or phrases (about, economic_model, network_versions, how_to_join, who_is_first_curator, service_status). This mix is readable but inconsistent.
With 30 tools, this exceeds the 25+ threshold that signals an overgrown surface. The broad scope—membership, authorities, operators, advocates, bans, campaigns, relays, and network info—partly justifies the count, but the set feels heavier than necessary and could be consolidated.
The tool surface covers the core lifecycle for citizens, operators, authorities, advocates, campaigns, and relays, plus governance and network status. Minor gaps exist—no advocate deregistration, no citizen update flow, and some ban tools are stubs—but agents can complete primary workflows.
On-chain ERC-8004 agent registry. Search, register, and check reputation across 16 chains.
Manage repositories, users, releases, and automate GitHub workflows
Access the GitHub API, enabling file operations, repository management, search functionality, and…
Read-only gateway for durable agent identity, consent, recognized work, and signed receipts.
