dpyc-oracle

dpyc-oracle — консьерж сообщества DPYC Social Contract: членство, управление, онбординг

От сообществаСбоиБез входаГлобальныйБесплатноТолько чтение

Что умеет

  • Искать участника и проверять статус блокировки
  • Получать свод правил и экономическую модель сети
  • Узнавать порядок вступления и подавать заявку на гражданство
  • Регистрировать оператора или авторитета
  • Проверять статус сервисов и релеев сети

Какие данные видит

Ассистент работает с публичными данными сообщества и реестрами участников без авторизации.

Нужен ли аккаунт

Не нужен: сервер работает без входа

dpyc-oracle помогает участникам сообщества DPYC Social Contract разобраться в правилах, ставках налога, порядке вступления и работе сети операторов. MCP-сервер бесплатный и отвечает на вопросы о членстве, регистрации авторитетов и статусе сервисов сети.

Как подключить

Как подключить dpyc-oracle к Claude

Адрес сервера, который нужно вставить в настройках Claude:

https://dpyc-oracle.fastmcp.app/mcp

  1. Откройте Claude (сайт claude.ai или приложение для компьютера).
  2. Перейдите в Настройки → Коннекторы (в английском интерфейсе: Settings → Connectors).
  3. Нажмите Добавить пользовательский коннектор (Add custom connector).
  4. Вставьте адрес сервера, скопированный ниже, в поле URL удалённого MCP-сервера и нажмите Добавить.
  5. В чате нажмите + → Коннекторы и включите новый коннектор.

Пользовательские коннекторы доступны на тарифах Free, Pro, Max, Team и Enterprise. На Free можно добавить только один. В Team и Enterprise коннектор сначала добавляет владелец организации в Настройки организации → Коннекторы.

Авторизация

После нажатия Добавить откроется окно входа в сервис. Войдите под своим аккаунтом и подтвердите доступ. Пароль Claude не видит.

Как подключить dpyc-oracle к ChatGPT

Адрес сервера, который нужно вставить в настройках ChatGPT:

https://dpyc-oracle.fastmcp.app/mcp

  1. Откройте ChatGPT в браузере (chatgpt.com). Нужен тариф Plus, Pro, Business, Enterprise или Edu.
  2. Один раз включите режим разработчика: Настройки → Приложения → Дополнительные настройки → Режим разработчика (Settings → Apps → Advanced settings → Developer mode).
  3. Откройте Настройки → Коннекторы и нажмите Создать (Create).
  4. Заполните форму: Название (любое), Описание (одна фраза, что делает сервис), URL MCP-сервера (скопируйте ниже).
  5. В поле Аутентификация выберите OAuth, если сервис требует вход, иначе Нет. Нажмите Создать.
  6. В новом чате откройте + → Приложения/Коннекторы и включите коннектор.

Название раздела у OpenAI менялось (Connectors → Apps/Plugins). Если пункт называется иначе, ищите «режим разработчика» в настройках. В рабочих пространствах Business/Enterprise администратор должен разрешить пользовательские коннекторы.

Авторизация

При первом использовании ChatGPT откроет окно входа в сервис. Войдите и подтвердите доступ.

Как подключить dpyc-oracle к Cursor

Адрес сервера, который нужно вставить в настройках Cursor:

https://dpyc-oracle.fastmcp.app/mcp

Быстрый способ: нажмите кнопку Открыть в Cursor ниже, Cursor сам предложит добавить сервер.

Вручную:

  1. В Cursor откройте Settings → Cursor Settings → MCP и нажмите Add new global MCP server.
  2. Вставьте JSON, скопированный ниже, в открывшийся файл ~/.cursor/mcp.json (для одного проекта: .cursor/mcp.json в корне проекта).
  3. Сохраните файл. Сервер появится в списке MCP; при необходимости пройдите авторизацию по кнопке рядом с ним.

Авторизация

Если сервис требует вход, рядом с сервером в списке MCP появится кнопка авторизации.

Список инструментов сервера (30)

Технические названия из tools/list. Нужны только разработчикам.

aboutExtended 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_memberLook 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_rateExplain 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``.
economic_modelExplain 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_rulebookFetch the DPYC Social Contract governance document. Returns the raw markdown of GOVERNANCE.md from the dpyc-community repo.
how_to_joinTier-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_curatorIdentify the First Curator (Prime Authority) of the Certification Chain. Returns the curator's npub, display name, and member record.
network_versionsGet 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_advisoryGet 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_authorityEnd-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.
service_statusDiagnostic: report this service's software versions and runtime info. Free, unauthenticated. Use to verify deployment versions across the DPYC ecosystem.
list_servicesEnumerate 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.
get_relaysReturn 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.
report_relay_failureReport 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.
resolve_authority_forResolve 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_serviceResolve 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_citizenshipBegin 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.
confirm_citizenshipComplete 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.
register_authorityRegister 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_operatorRegister 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.
update_operatorUpdate 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).
deregister_operatorRemove 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.
register_advocateRegister 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.
check_ban_statusCheck 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.
renounce_membershipCitizen 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_electionInitiate 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_voteCast 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_campaignPublish 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.
list_campaignsList published pricing campaigns from the DPYC community. Optionally filter by operator or author npub.
get_campaignRetrieve a published pricing campaign.