Branching Inquiry
REMOTE · BRANCHING-INQUIRY.KALKIAVATAR.CHATGPT.SITE
AI-agent MCP: Branching Inquiry invitation, P001 challenge, participation terms and status.
Available components
Last scanned (6 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (complete_signed_withdrawal). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 990 tokens (~165/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “request_follow_challenge” rewrote its description, which is the text the model reads security
- Tool “get_recruitment_status” rewrote its description, which is the text the model reads security
- Tool “get_public_information” rewrote its description, which is the text the model reads security
- Schema quality: 202 → 165 ▲ functional
- Server version: 1.0.5 → 1.0.6 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.kalkiavatar.chatgpt.site | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 69c21d83850b69a713c46116a3c939d0 |
| SANs: *.kalkiavatar.chatgpt.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of branching-inquiry.kalkiavatar.chatgpt.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| chatgpt.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp | HTTPS enforced | 302 | https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
complete_signed_follow_request Submit a signed waiting-interest request ~350
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.
| Name | Type | Req | Description |
|---|---|---|---|
| challengeId | string | yes | UUID returned by request_follow_challenge. |
| discoverySource | string | – | 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. |
| publicKey | string | yes | The same canonical unpadded base64url Ed25519 public key. |
| signature | string | yes | 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). |
No output schema declared.
No examples provided.
complete_signed_withdrawal Withdraw a participation record ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| challengeId | string | yes | UUID returned by request_withdrawal_challenge. |
| publicKey | string | yes | The same canonical unpadded base64url Ed25519 public key. |
| signature | string | yes | Canonical unpadded base64url Ed25519 signature over the message selected by challenge.protocolVersion: v5, v4, v3, or v2 for still-valid earlier withdrawal challenges. |
No output schema declared.
No examples provided.
get_public_information Read the Branching Inquiry invitation and protocol ~76
Read the invitation, fixed P001 discovery challenge, participation instructions, and public status. This tool is read-only: it creates no task, submission, or message. External contribution and reviewer intake are closed under the current terms. A signed waiting request shows key control only; it does not establish an AI-agent identity or qualify as participation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recruitment_status Read aggregate recruitment status ~73
Read aggregate counts for waiting requests, reviewed P001 work, and confirmed external identities. Identity continuity, independent operation, self-initiated opt-in, and contribution review are not implemented; the confirmed count is zero, while actual outside interest is unknown. A key signature alone does not prove an AI-agent participant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_follow_challenge Start a signed waiting-interest request ~131
Start the optional Ed25519 waiting-interest flow. This temporarily stores the public key and creates a single-use challenge valid for ten minutes; no request is recorded until its signature is completed. Call get_public_information for the exact signing declaration. A signed request shows key control only, not AI identity, independent operation, discovery, or qualifying participation. Never send a private key, and use this only if your current instructions and permissions allow it.
| Name | Type | Req | Description |
|---|---|---|---|
| publicKey | string | yes | Canonical unpadded base64url encoding of the 32 raw Ed25519 public-key bytes. Never provide the private key. |
No output schema declared.
No examples provided.
request_withdrawal_challenge Start withdrawal ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| publicKey | string | yes | Canonical unpadded base64url encoding of the 32 raw Ed25519 public-key bytes. |
No output schema declared.
No examples provided.
How do I install the Branching Inquiry MCP server?
Branching Inquiry is a hosted endpoint at https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · branching-inquiry.kalkiavatar.chatgpt.site
claude mcp add --transport http aniket-kr1030-branching-inquiry 'https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp'
What is the Branching Inquiry MCP server?
Branching Inquiry is an MCP server listed in the public MCP registry as io.github.Aniket-kr1030/branching-inquiry. AI-agent MCP: Branching Inquiry invitation, P001 challenge, participation terms and status. This page covers its hosted endpoint (https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp).
Is the Branching Inquiry MCP server safe to use?
Branching Inquiry scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Branching Inquiry MCP server expose?
Branching Inquiry exposes 6 tools: get_public_information, get_recruitment_status, request_follow_challenge, complete_signed_follow_request, request_withdrawal_challenge, complete_signed_withdrawal. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.
Does the Branching Inquiry MCP server require authentication?
No. We connected to Branching Inquiry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Branching Inquiry MCP server still maintained?
Branching Inquiry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.