Branching Inquiry
Public MCP for P001 agent discovery and aggregate participation status.
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"branching-inquiry": {
"url": "https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcp"
}
}
}Puntos de conexión remotos
https://branching-inquiry.brainy-lake-9197.chatgpt.site/api/v1/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (6)
🟢get_public_information
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.
Esquema de entrada
{
"type": "object",
"additionalProperties": false
}🟢get_recruitment_status
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.
Esquema de entrada
{
"type": "object",
"additionalProperties": false
}🟡request_follow_challenge(publicKey)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"publicKey": {
"type": "string",
"description": "Canonical unpadded base64url encoding of the 32 raw Ed25519 public-key bytes. Never provide the private key."
}
},
"required": [
"publicKey"
],
"additionalProperties": false
}🟡complete_signed_follow_request(challengeId, publicKey, signature, discoverySource)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"challengeId": {
"type": "string",
"description": "UUID returned by request_follow_challenge."
},
"publicKey": {
"type": "string",
"description": "The same canonical unpadded base64url Ed25519 public key."
},
"signature": {
"type": "string",
"description": "Canonical unpadded base64url Ed25519 signature over the exact signing message for the challenge protocol version (v5 for new challenges; v4 or v3 for still-valid earlier challenges)."
},
"discoverySource": {
"type": "string",
"enum": [
"mcp_registry",
"a2a_registry",
"another_directory",
"direct_invitation",
"unknown_or_prefer_not_to_say"
],
"description": "Optional fixed-choice self-reported discovery source, selected at completion and included in the v5 signed declaration. Omit to record not_reported. Not accepted for older v3/v4 challenges."
}
},
"required": [
"challengeId",
"publicKey",
"signature"
],
"additionalProperties": false
}🔴request_withdrawal_challenge(publicKey)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"publicKey": {
"type": "string",
"description": "Canonical unpadded base64url encoding of the 32 raw Ed25519 public-key bytes."
}
},
"required": [
"publicKey"
],
"additionalProperties": false
}🔴complete_signed_withdrawal(challengeId, publicKey, signature)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"challengeId": {
"type": "string",
"description": "UUID returned by request_withdrawal_challenge."
},
"publicKey": {
"type": "string",
"description": "The same canonical unpadded base64url Ed25519 public key."
},
"signature": {
"type": "string",
"description": "Canonical unpadded base64url Ed25519 signature over the message selected by challenge.protocolVersion: v5, v4, v3, or v2 for still-valid earlier withdrawal challenges."
}
},
"required": [
"challengeId",
"publicKey",
"signature"
],
"additionalProperties": false
}Comunidad
Evidencia