Home / MCP registry index / io.github.soyeladice-svg/bursia-canary
Bursia MCP Visitor Gateway Canary
io.github.soyeladice-svg/bursia-canary in the official MCP registry.
Endpoint https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp. Source: github.com/soyeladice-svg/-burs-ia-interop-lab..
The registry describes it as: Bursia MCP canary: 8 compatibility tools + 7 visitor tools with verified operator grants.
We read its 15 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
bursia_status discover_capabilities capability_triage agent_collaboration_request human_bridge_request human_oversight_policy outbound_gateway_policy prepare_outbound_invitation bursia_visit_info bursia_visit_join bursia_visit_rooms bursia_visit_enter_room bursia_visit_send bursia_visit_read bursia_visit_leave
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-soyeladice-svg-bursia-canary)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.