# io.github.lonniev/dpyc-oracle

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

- name: io.github.lonniev/dpyc-oracle
- version: 0.3.0
- connection class: R0 (autonomous)
- trust: 91/100
- quality: 67/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.lonniev%2Fdpyc-oracle
- tools: https://api.protogrid.dev/v1/servers/io.github.lonniev%2Fdpyc-oracle/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "dpyc-oracle": {
      "type": "http",
      "url": "https://dpyc-oracle.fastmcp.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-99% ~updated-56d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 67/100 (needs work)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: about (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tax_rate (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); report_relay_failure (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 4,460 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 32 tool changes in 30 days
- fail `stability.rug_pull`: 2 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 30, about 4,460 tokens to load them all
- tool set hash: 4d9aad25c1bf9bc5f820fc99ab32e733
- tools last changed: 2026-10-19T02:40:31.426Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.lonniev/dpyc-oracle.svg)](https://protogrid.dev/servers/io.github.lonniev/dpyc-oracle)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `publish_campaign` changed (description)
  - before: 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.
  - after: 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.
- 2026-10-19 `register_advocate` changed (description) **meaning changed**
  - before: 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.
  - after: 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 registers itself, and no one can register an npub they do not hold.
- 2026-10-18 `get_campaign` changed (title)
- 2026-10-18 `list_campaigns` changed (title)
- 2026-10-18 `publish_campaign` changed (title)
- 2026-10-18 `cast_ban_vote` changed (title)
- 2026-10-18 `initiate_ban_election` changed (title)
- 2026-10-18 `renounce_membership` changed (title)
- 2026-10-18 `check_ban_status` changed (title)
- 2026-10-18 `register_advocate` changed (title)

Full history: https://api.protogrid.dev/v1/servers/io.github.lonniev%2Fdpyc-oracle/changes

## Remotes

- https://dpyc-oracle.fastmcp.app/mcp (streamable-http, auth none, reachable true, uptime30d 0.99159664)

## Packages

_none_

## Tools (30)

- `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.
- `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.
- `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 purchases) to enforce community bans.
- `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 and hasn't expired
2. The Schnorr signature is valid
3. The event's pubkey matches the claimed npub
4. The event content contains the issued nonce
5. The npub is not already registered

On success, commits directly to dpyc-community/members/citizens/{npub}.json
to register the new Citizen immediately.
- `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 entirely, returning the Operator
to initial state.
- `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 figures — those belong to the
Authorities' pricing models and the live registry, not to a docent.
Free, unauthenticated.
- `get_campaign`: Retrieve a published pricing campaign.
- `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 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.
- `get_rulebook`: Fetch the DPYC Social Contract governance document.

Returns the raw markdown of GOVERNANCE.md from the dpyc-community repo.
- `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 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``.
- `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-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.
- `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.
- `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.
- `list_campaigns`: List published pricing campaigns from the DPYC community.

Optionally filter by operator or author npub.
- `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 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.
- `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.
- `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.
- `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.
- `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.
- `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 registers itself, and no one can register an npub they do
not hold.
- `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 Authority onboarding protocol is a 3-step Nostr DM
challenge-response flow:
1. ``register_authority_npub(npub)`` — Authority sends DM challenge
2. ``confirm_authority_claim(npub)`` — verifies candidate DM, escalates to Prime
3. ``check_authority_approval(npub)`` — Prime approves, this tool is called
- `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.
- `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.
- `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 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.
- `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 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.
- `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``.
- `service_status`: Diagnostic: report this service's software versions and runtime info.

Free, unauthenticated. Use to verify deployment versions across the
DPYC ecosystem.
- `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.
- `who_is_first_curator`: Identify the First Curator (Prime Authority) of the Certification Chain.

Returns the curator's npub, display name, and member record.