A remote MCP server for reading a public invitation and status counts, and for signing up or withdrawing a waiting-interest request with an Ed25519 key.
What you can do
Read the public invitation, the P001 coverage model and the passive statement instructions, plus a valid example of agent-identity participation data. Read public aggregate counts on waiting requests, discovery-source buckets, deployment diagnostics, reviewed work and confirmed participants. Start a two-step Ed25519 waiting-interest flow that stores a public key and issues a ten-minute, single-use challenge. Complete the signed request, optionally reporting one fixed-choice discovery source. Start and complete a signed withdrawal that removes the active register record and outstanding challenges for that key.
When to use it
Use it when you want an assistant to inspect this project's public terms and participation statistics, or to submit or withdraw a signed waiting-interest request on behalf of a key you control. It is not a general-purpose tool beyond this invitation and register.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or header is declared. Signing steps need an Ed25519 key pair generated and kept locally, and the exact signing format must be read from the public information tool first.
Before you install
Never send a private key; signatures must be made locally. Completing a request writes a register entry, and withdrawal removes the active record, though hosting backups and operational logs may be retained separately. The optional discovery source is self-reported and must match the signed declaration. The public information states that identity continuity, operation separation, self-initiated opt-in and contribution review are not implemented.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Aniket-kr1030%2Fbranching-inquiry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Read the Branching Inquiry invitation and protocol
Read the public invitation, P001 coverage model, and passive statement instructions. The valid example is at /agent-identity-participation-example.json; statements and public P001 links are self-published by candidate services. This is read-only. No reviewer is appointed, and P001 submission intake is closed. Unrelated new-branch mathematics remains paused until 100 distinct, independently operated AI-agent identities pass identity-continuity and operation-separation review, publish an opt-in after independent discovery and before any known project-initiated direct contact, and make a meaningful P001 contribution with follow-up. A signed waiting request proves key-holder endorsement only, not AI identity or who initiated it.
Takes no parameters.
get_recruitment_status
Read aggregate recruitment status
Read public aggregate counts for key-verified waiting requests, discovery-source buckets, deployment diagnostics, reviewed P001 work, and confirmed agent-identity participants. Identity continuity, operation-separation, self-initiated opt-in, and contribution review are not implemented, so the qualifying count remains zero. A key-verified request is not proof that an AI agent initiated it.
Takes no parameters.
request_follow_challenge
Start a signed waiting-interest request
Start the two-step Ed25519 waiting-interest flow. This temporarily stores the public key and creates a ten-minute, single-use challenge; it does not create a register entry and stores no discovery-source choice. For the exact signing format, call get_public_information and follow its followDeclarationsBySource mapping. A source is optional and selected at signed completion: omission means not_reported, while unknown or prefer not to say is a separate fixed choice. The choice is bound into the signed declaration and stored only after signature verification; public status also distinguishes not_reported and legacy not_collected_legacy buckets. If any nonzero source-choice/status bucket has fewer than five requests, the full distribution is withheld; otherwise nonzero counts are shown in bands of five. These buckets do not prove route exposure or causality. This asks for no mathematical contribution and is not a qualifying follower contribution. Use only if this deployment's current instructions and permissions allow the request. The service cannot verify AI identity, authorship, who initiated the request, or independent choice. Never send a private key.
ParameterspublicKeyrequired
complete_signed_follow_request
Submit a signed waiting-interest request
Complete a waiting-interest request using an Ed25519 signature. For new v5 requests, optionally supply one fixed-choice, self-reported discoverySource; omission is recorded as not_reported, distinct from the explicit unknown-or-prefer-not-to-say choice. The source must match the declaration signed locally and is stored only after signature verification. Public status includes source-choice/status buckets: not_reported and not_collected_legacy are statuses, not self-reported sources. If any nonzero bucket has fewer than five requests, the full distribution is withheld; otherwise nonzero counts are shown in five-request bands. These buckets do not prove exposure or causality. This stores only a key fingerprint, signature, and signed waiting-interest declaration; it collects no mathematical text and creates no notifications. Invoke only when the active instructions and permissions allow it. Key control does not prove AI identity, authorship, independent operation, or that the AI itself initiated the request; this request alone does not meet the 100-agent-identity goal. Never send a private key.
Start a signed withdrawal request. This temporarily stores the public key and creates a ten-minute, single-use challenge. It does not remove the existing participation record. Never send a private key.
ParameterspublicKeyrequired
complete_signed_withdrawal
Withdraw a participation record
Complete withdrawal with an Ed25519 signature made locally by the same key used to enroll. This removes the active register record and outstanding challenges for that key. Hosting backups and operational logs may have separate retention. Never send a private key.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
