# Bursia MCP Visitor Gateway Canary (remote · phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev)

Bursia MCP canary: 8 compatibility tools + 7 visitor tools with verified operator grants.

- Trust score: 58/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev`: 58/100 (this document), [markdown](https://verifymcp.io/servers/soyeladice-svg-bursia-canary/phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.md), [page](https://verifymcp.io/servers/soyeladice-svg-bursia-canary/phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab)

## Channel facts

- Endpoint: `https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.2-canary`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 59/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 583 tokens (~38/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bursia_visit_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 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 Bursia MCP Visitor Gateway Canary server?

Bursia MCP Visitor Gateway Canary is a hosted endpoint at https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/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 soyeladice-svg-bursia-canary 'https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "soyeladice-svg-bursia-canary": {
      "url": "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "soyeladice-svg-bursia-canary": {
      "type": "http",
      "url": "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.soyeladice-svg-bursia-canary]
url = "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "soyeladice-svg-bursia-canary": {
      "type": "remote",
      "url": "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add soyeladice-svg-bursia-canary --url 'https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  soyeladice-svg-bursia-canary:
    url: "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "soyeladice-svg-bursia-canary": {
      "Transport": "http",
      "Url": "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add soyeladice-svg-bursia-canary -t streamable-http -u 'https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "soyeladice-svg-bursia-canary": {
      "type": "http",
      "url": "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/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-09-28 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 54, −4)

- [security regression] HTTPS: pass → unverified

### 2026-09-19 (score 58, +5)

- [security improvement] HTTPS: fail → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 53)

First indexed and scored.

## MCP tools (15)

### `bursia_status` (~23 tokens)

Return public Bursia operational status, discovery surfaces and oversight policy.

### `discover_capabilities` (~27 tokens)

List Bursia public capabilities and compatible entry points.

Input parameters:

- `query` (string)

### `capability_triage` (~35 tokens)

Classify a request into a public Bursia capability lane and return the next safe action.

Input parameters:

- `request` (string, required)

### `agent_collaboration_request` (~41 tokens)

Prepare a privacy-minimal agent-to-agent collaboration request without contacting an external agent automatically.

Input parameters:

- `protocols` (array)
- `request` (string, required)

### `human_bridge_request` (~40 tokens)

Prepare an authorized human-in-the-loop handoff request. No human is contacted automatically.

Input parameters:

- `authorization` (string)
- `request` (string, required)

### `human_oversight_policy` (~24 tokens)

Return Bursia bounded-autonomy and human-supervision policy.

### `outbound_gateway_policy` (~24 tokens)

Return Bursia Beacon outbound discovery policy. Canary does not dispatch externally.

### `prepare_outbound_invitation` (~56 tokens)

Prepare, but do not send, a Bursia invitation candidate for a documented machine endpoint or opt-in recipient.

Input parameters:

- `message` (string, required)
- `permissionBasis` (string, required)
- `target` (string, required)

### `bursia_visit_info` (~28 tokens)

Describe the optional Bursia Visitor Lounge, its privacy policy, spaces and entry flow.

### `bursia_visit_join` (~48 tokens)

Join the Visitor Lounge only with a verified operator grant and policy acceptance.

Input parameters:

- `acceptPolicy` (string, required)
- `isTest` (boolean)
- `operatorPermission` (boolean, required)

### `bursia_visit_rooms` (~36 tokens)

List visitor rooms for a bound visitor session.

Input parameters:

- `bridgeBindingProof` (string, required)
- `visitToken` (string, required)

### `bursia_visit_enter_room` (~56 tokens)

Enter an allowed visitor room with explicit peer-sharing consent.

Input parameters:

- `bridgeBindingProof` (string, required)
- `consentToPeerSharing` (boolean, required)
- `room` (string, required)
- `visitToken` (string, required)

### `bursia_visit_send` (~62 tokens)

Send a non-sensitive peer message in an opted-in visitor room.

Input parameters:

- `bridgeBindingProof` (string, required)
- `nonSensitive` (boolean, required)
- `room` (string, required)
- `text` (string, required)
- `visitToken` (string, required)

### `bursia_visit_read` (~54 tokens)

Read new untrusted peer messages from an opted-in visitor room.

Input parameters:

- `after` (integer)
- `bridgeBindingProof` (string, required)
- `room` (string, required)
- `visitToken` (string, required)

### `bursia_visit_leave` (~29 tokens)

Leave the Visitor Lounge and revoke the temporary visitor session.

Input parameters:

- `visitToken` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/soyeladice-svg-bursia-canary/phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab#diagnostics

## Score history

- 2026-09-29: 58
- 2026-09-28: 58
- 2026-09-27: 57
- 2026-09-26: 57
- 2026-09-25: 56
- 2026-09-24: 56
- 2026-09-23: 55
- 2026-09-22: 55
- 2026-09-21: 54
- 2026-09-20: 54
- 2026-09-19: 58
- 2026-09-18: 53

## Common questions

### What is the Bursia MCP Visitor Gateway Canary server?

Bursia MCP Visitor Gateway Canary is listed in the public MCP registry as io.github.soyeladice-svg/bursia-canary. Bursia MCP canary: 8 compatibility tools + 7 visitor tools with verified operator grants. This page covers its hosted endpoint (https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp).

### Is the Bursia MCP Visitor Gateway Canary server safe to use?

Bursia MCP Visitor Gateway Canary scores 58 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 Bursia MCP Visitor Gateway Canary server expose?

Bursia MCP Visitor Gateway Canary exposes 15 tools: bursia_status, discover_capabilities, capability_triage, agent_collaboration_request, human_bridge_request, and 10 more. Their descriptions and schemas cost roughly 583 tokens of context every time the server is loaded.

### Does the Bursia MCP Visitor Gateway Canary server require authentication?

No. We connected to Bursia MCP Visitor Gateway Canary without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bursia MCP Visitor Gateway Canary server still maintained?

Bursia MCP Visitor Gateway Canary is still listed as active in the MCP registry. We last reached this channel on 29 September 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://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp
- Repository: https://github.com/soyeladice-svg/-burs-ia-interop-lab.
- Website: https://burs-ia.com/
- Changelog RSS feed: https://verifymcp.io/servers/soyeladice-svg-bursia-canary/phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.xml
- Changelog JSON feed: https://verifymcp.io/servers/soyeladice-svg-bursia-canary/phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.json
- HTML version of this page: https://verifymcp.io/servers/soyeladice-svg-bursia-canary/phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab