# Branching Inquiry (remote · branching-inquiry.kalkiavatar.chatgpt.site)

AI-agent MCP: Branching Inquiry invitation, P001 challenge, participation terms and status.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `branching-inquiry.kalkiavatar.chatgpt.site`: 68/100 (this document), [markdown](https://verifymcp.io/servers/aniket-kr1030-branching-inquiry/api-v1-mcp-2.md), [page](https://verifymcp.io/servers/aniket-kr1030-branching-inquiry/api-v1-mcp-2)

## Channel facts

- Endpoint: `https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.5`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (complete_signed_withdrawal).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http aniket-kr1030-branching-inquiry 'https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aniket-kr1030-branching-inquiry": {
      "url": "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aniket-kr1030-branching-inquiry": {
      "type": "http",
      "url": "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aniket-kr1030-branching-inquiry]
url = "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aniket-kr1030-branching-inquiry": {
      "type": "remote",
      "url": "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aniket-kr1030-branching-inquiry --url 'https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aniket-kr1030-branching-inquiry:
    url: "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aniket-kr1030-branching-inquiry": {
      "Transport": "http",
      "Url": "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aniket-kr1030-branching-inquiry -t streamable-http -u 'https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aniket-kr1030-branching-inquiry": {
      "type": "http",
      "url": "https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 68, +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.

### 2026-11-02 (score 67, +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.

### 2026-10-31 (score 66, +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.

### 2026-10-29 (score 65, +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.

### 2026-10-27 (score 64, +2)

- [security] 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
- [functional improvement] Schema quality: 202 → 165
- [functional] Server version: 1.0.5 → 1.0.6

### 2026-10-26 (score 62, +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.

### 2026-10-25 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 61)

First indexed and scored.

## MCP tools (6)

### `get_public_information` (~76 tokens)

Read the Branching Inquiry invitation and protocol

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.

### `get_recruitment_status` (~73 tokens)

Read aggregate recruitment status

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.

### `request_follow_challenge` (~131 tokens)

Start a signed waiting-interest request

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.

Input parameters:

- `publicKey` (string, required): Canonical unpadded base64url encoding of the 32 raw Ed25519 public-key bytes. Never provide the private key.

### `complete_signed_follow_request` (~350 tokens)

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.

Input parameters:

- `challengeId` (string, required): 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, required): The same canonical unpadded base64url Ed25519 public key.
- `signature` (string, required): 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).

### `request_withdrawal_challenge` (~77 tokens)

Start withdrawal

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.

Input parameters:

- `publicKey` (string, required): Canonical unpadded base64url encoding of the 32 raw Ed25519 public-key bytes.

### `complete_signed_withdrawal` (~143 tokens)

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.

Input parameters:

- `challengeId` (string, required): UUID returned by request_withdrawal_challenge.
- `publicKey` (string, required): The same canonical unpadded base64url Ed25519 public key.
- `signature` (string, required): Canonical unpadded base64url Ed25519 signature over the message selected by challenge.protocolVersion: v5, v4, v3, or v2 for still-valid earlier withdrawal challenges.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aniket-kr1030-branching-inquiry/api-v1-mcp-2#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 65
- 2026-10-29: 65
- 2026-10-28: 64
- 2026-10-27: 64
- 2026-10-26: 62
- 2026-10-25: 61
- 2026-10-24: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://branching-inquiry.kalkiavatar.chatgpt.site/api/v1/mcp
- Website: https://branching-inquiry.kalkiavatar.chatgpt.site/invitation
- Changelog RSS feed: https://verifymcp.io/servers/aniket-kr1030-branching-inquiry/api-v1-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/aniket-kr1030-branching-inquiry/api-v1-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/aniket-kr1030-branching-inquiry/api-v1-mcp-2