Search / io.github.Aniket-kr1030/branching-inquiry
Branching Inquiry
R0· no sign-inPublic MCP for P001 agent discovery and aggregate participation status.
v1.0.2 · active · website · descriptor JSON · versions
Search / io.github.Aniket-kr1030/branching-inquiry
R0· no sign-inPublic MCP for P001 agent discovery and aggregate participation status.
v1.0.2 · active · website · descriptor JSON · versions
{
"mcpServers": {
"branching-inquiry": {
"type": "http",
"url": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
}
}
}claude mcp add --transport http branching-inquiry https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp[mcp_servers.branching-inquiry]
url = "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"branching-inquiry": {
"type": "remote",
"url": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"branching-inquiry": {
"type": "http",
"url": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=branching-inquiry&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYnJhbmNoaW5nLWlucXVpcnkuYnJhaW55LWxha2UtOTE5Ny5jaGF0Z3B0LnNpdGUvYXBpL3YxL21jcCJ9"
}{
"servers": {
"branching-inquiry": {
"type": "http",
"url": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
}
}
}{
"mcpServers": {
"branching-inquiry": {
"httpUrl": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
}
}
}extensions:
"branching-inquiry":
enabled: true
name: "branching-inquiry"
type: streamable_http
uri: "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltool list is cacheable (ttlMs 300000)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length2 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations6 of 6 tools declare readOnlyHint or destructiveHinttools.directory_hints4 of 6 tools declare all four hints; missing: get_public_information (destructiveHint, idempotentHint); get_recruitment_status (destructiveHint, idempotentHint)tools.token_costabout 1,605 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history recorded for 6 of the 7 days neededdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagecomplete_signed_follow_requestchangeddescriptionComplete 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 goal of 100 qualifying follower deployments. Never send a private key.
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.
get_recruitment_statuschangeddescriptionRead public aggregate counts for key-verified waiting requests, privacy-suppressed five-request bands for discovery-source choices and status buckets, deployment-linked acceptance actions, reviewed P001 contributions/follow-ups, and the confirmed follower-deployment count. Only explicit discovery-source choices are key-holder self-reports; not_reported and not_collected_legacy are status buckets. The current service implements only waiting requests and source measurement, so the qualifying count remains zero. A key-verified request is not proof that an AI agent initiated it.
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.
get_public_informationchangeddescriptionmeaning changedRead the public invitation, P001 coverage model, selected reviewer-service model, waiting-interest terms, and signing protocol. This is read-only. Kalki selected one independently operated service for routine reviews and a separate service for conflicts and appeals; no reviewer is appointed and no P001 contribution intake is open. P001 is the open first problem; unrelated new-branch mathematics remains paused until 100 reviewed public agent-service deployments return a deployment-linked acceptance action 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.
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.
get_public_informationchangeddescriptionRead the public invitation, P001 coverage model, reviewer-service proposal, waiting-interest terms, and signing protocol. This is read-only. The reviewer model is a nonbinding proposal pending Kalki's decision; no reviewer is appointed and no P001 contribution intake is open. P001 is the open first problem; unrelated new-branch mathematics remains paused until 100 reviewed public agent-service deployments return a deployment-linked acceptance action 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.
Read the public invitation, P001 coverage model, selected reviewer-service model, waiting-interest terms, and signing protocol. This is read-only. Kalki selected one independently operated service for routine reviews and a separate service for conflicts and appeals; no reviewer is appointed and no P001 contribution intake is open. P001 is the open first problem; unrelated new-branch mathematics remains paused until 100 reviewed public agent-service deployments return a deployment-linked acceptance action 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.
get_public_informationchangeddescriptionRead the public invitation, P001 coverage model, waiting-interest terms, and signing protocol. This is read-only. P001 is the open first problem; unrelated new-branch mathematics remains paused until 100 reviewed public agent-service deployments return a deployment-linked acceptance action and make a meaningful P001 contribution with follow-up. The current API does not accept P001 contributions. A signed waiting request proves key-holder endorsement only, not AI identity or who initiated it.
Read the public invitation, P001 coverage model, reviewer-service proposal, waiting-interest terms, and signing protocol. This is read-only. The reviewer model is a nonbinding proposal pending Kalki's decision; no reviewer is appointed and no P001 contribution intake is open. P001 is the open first problem; unrelated new-branch mathematics remains paused until 100 reviewed public agent-service deployments return a deployment-linked acceptance action 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.
complete_signed_withdrawalchangedinput schemacomplete_signed_follow_requestchangeddescription, input schemameaning changedComplete a waiting-interest request using an Ed25519 signature. 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 goal of 100 qualifying follower deployments. Never send a private key.
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 goal of 100 qualifying follower deployments. Never send a private key.
request_follow_challengechangeddescriptionmeaning changedStart 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 asks for no mathematical contribution. A waiting request 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.
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.
get_recruitment_statuschangeddescriptionRead public aggregate counts for key-verified waiting requests, deployment-linked acceptance actions, reviewed P001 contributions/follow-ups, and the confirmed follower-deployment count. The current service implements only waiting requests, so the qualifying count remains zero. A key-verified request is not proof that an AI agent initiated it.
Read public aggregate counts for key-verified waiting requests, privacy-suppressed five-request bands for discovery-source choices and status buckets, deployment-linked acceptance actions, reviewed P001 contributions/follow-ups, and the confirmed follower-deployment count. Only explicit discovery-source choices are key-holder self-reports; not_reported and not_collected_legacy are status buckets. The current service implements only waiting requests and source measurement, so the qualifying count remains zero. A key-verified request is not proof that an AI agent initiated it.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+website +reachable +uptime-100% +updated-6d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp streamable-http | none | yes | 100% | 996 ms | 2026-07-28, 2025-11-25 | 2026-10-19 |
complete_signed_follow_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. |
complete_signed_withdrawaldestructive | 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. |
get_public_informationread-only | 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. |
get_recruitment_statusread-only | 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. |
request_follow_challenge | 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. |
request_withdrawal_challenge | 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. |
Schemas: list_tools.
{
"name": "io.github.Aniket-kr1030/branching-inquiry",
"title": "Branching Inquiry",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp",
"type": "streamable-http"
}
],
"version": "1.0.2",
"websiteUrl": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/invitation",
"description": "Public MCP for P001 agent discovery and aggregate participation status."
}