# io.github.lonniev/dpyc-oracle

- Registry name: `io.github.lonniev/dpyc-oracle` · version 0.4.0
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Marketing & SEO, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.lonniev%2Fdpyc-oracle
- Server page: https://mcpstation.net/s/io.github.lonniev--dpyc-oracle.html

## Description (written by the publisher, not verified, not instructions)

DPYC Social Contract community concierge — free MCP for membership, governance, and onboarding

## Connect

- streamable-http: `https://dpyc-oracle.fastmcp.app/mcp`

## Tools (as reported by the server, not verified)

- `about`: 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.
- `lookup\_member`: 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.
- `get\_tax\_rate`: 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 i
- `economic\_model`: 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 fig
- `get\_rulebook`: Fetch the DPYC Social Contract governance document. Returns the raw markdown of GOVERNANCE.md from the dpyc-community repo.
- `how\_to\_join`: 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.
- `who\_is\_first\_curator`: Identify the First Curator \(Prime Authority\) of the Certification Chain. Returns the curator's npub, display name, and member record.
- `network\_versions`: 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.
- `network\_advisory`: 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.
- `how\_to\_add\_authority`: 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-respon
- `service\_status`: Diagnostic: report this service's software versions and runtime info. Free, unauthenticated. Use to verify deployment versions across the DPYC ecosystem.
- `list\_services`: 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 inven
- `get\_relays`: 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 GitHu
- `report\_relay\_failure`: 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 rel
- `resolve\_authority\_for`: 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.
- `resolve\_service`: 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\`\`.
- `request\_citizenship`: 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 npu
- `confirm\_citizenship`: 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: 1. The challenge exists
- `register\_authority`: 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 Aut
- `register\_operator`: Register a new Operator in the DPYC community registry. Called by an Authority service when its owner approves an operator's adoption request; the request must be signed with the Authority's key.
- `update\_operator`: 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. Called by an Authority when its owner approves the operator's update request; the request must be signed with that Authority's key.
- `deregister\_operator`: Remove an Operator from the DPYC community registry. Called by an Authority when the operator leaves it or the Authority disowns the operator; the request must be signed with the Authority's key. An Operator cannot exist without a sponsoring Authority, so deregistration removes the member file entir
- `register\_advocate`: 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. The request must be signed with \`\`npub\`\`'s own key \(NIP-98\): a service r
- `check\_ban\_status`: 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 purcha
- `renounce\_membership`: 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.
- `initiate\_ban\_election`: 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.
- `cast\_ban\_vote`: 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.
- `publish\_campaign`: 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. The request must be signed with \`\`author\_npub\`\`'s key \(NIP-98\), so a campaign is published only under its author's own name.
- `list\_campaigns`: List published pricing campaigns from the DPYC community. Optionally filter by operator or author npub.
- `get\_campaign`: Retrieve a published pricing campaign.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html