Bursia MCP Visitor Gateway Canary
io.github.soyeladice-svg/bursia-canarysoyeladice-svgstreamable-httpv0.7.2-canaryScanned
Bursia MCP canary: 8 compatibility tools + 7 visitor tools with verified operator grants.
15 tools: 1 do something that can't be undone, 7 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
8 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Bursia MCP Visitor Gateway Canary can do
The Bursia MCP Visitor Gateway Canary is published by the GitHub account soyeladice-svg. It has 15 tools. It can do things that cannot be undone, such as sending, paying or publishing (bursia_visit_send) and create or change data (7 tools: capability_triage, agent_collaboration_request, human_bridge_request, prepare_outbound_invitation and 3 more), but cannot delete data. 7 tools only read.
1 tool reads private data (bursia_visit_read); 1 tool brings in text other people can write (bursia_visit_read); 1 tool can send data out of your system (bursia_visit_send). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 21, 2026, version 0.7.2-canary.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Can't be undone 1Claude Code: ask
bursia_visit_sendSend a non-sensitive peer message in an opted-in visitor room.Can send data outNo findings
Why it is in this group
- The name "bursia_visit_send" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "bursia_visit_send" says "send": it sends or publishes something to other people.
Description, as the server wrote it Send a non-sensitive peer message in an opted-in visitor room.
Changes things 7Claude Code: ask
agent_collaboration_requestPrepare a privacy-minimal agent-to-agent collaboration request without contacting an external agent automatically.No findings
Why it is in this group
- The name "agent_collaboration_request" says "request": a word for a change.
Description, as the server wrote it Prepare a privacy-minimal agent-to-agent collaboration request without contacting an external agent automatically.
bursia_visit_enter_roomEnter an allowed visitor room with explicit peer-sharing consent.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Enter an allowed visitor room with explicit peer-sharing consent.
bursia_visit_joinJoin the Visitor Lounge only with a verified operator grant and policy acceptance.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Join the Visitor Lounge only with a verified operator grant and policy acceptance.
bursia_visit_leaveLeave the Visitor Lounge and revoke the temporary visitor session.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Leave the Visitor Lounge and revoke the temporary visitor session.
capability_triageClassify a request into a public Bursia capability lane and return the next safe action.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Classify a request into a public Bursia capability lane and return the next safe action.
human_bridge_requestPrepare an authorized human-in-the-loop handoff request.No findings
Why it is in this group
- The name "human_bridge_request" says "request": a word for a change.
Description, as the server wrote it Prepare an authorized human-in-the-loop handoff request. No human is contacted automatically.
prepare_outbound_invitationPrepare, but do not send, a Bursia invitation candidate for a documented machine endpoint or opt-in recipient.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prepare, but do not send, a Bursia invitation candidate for a documented machine endpoint or opt-in recipient.
Only reads 7Show 7 read-only tools
bursia_statusReturn public Bursia operational status, discovery surfaces and oversight policy.No findings
Why it is in this group
- The name "bursia_status" says "status": a word for reading.
Description, as the server wrote it Return public Bursia operational status, discovery surfaces and oversight policy.
bursia_visit_infoDescribe the optional Bursia Visitor Lounge, its privacy policy, spaces and entry flow.No findings
Why it is in this group
- The description's first verb is "describe": a word for reading.
Description, as the server wrote it Describe the optional Bursia Visitor Lounge, its privacy policy, spaces and entry flow.
bursia_visit_readRead new untrusted peer messages from an opted-in visitor room.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "bursia_visit_read" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
Description, as the server wrote it Read new untrusted peer messages from an opted-in visitor room.
bursia_visit_roomsList visitor rooms for a bound visitor session.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List visitor rooms for a bound visitor session.
discover_capabilitiesList Bursia public capabilities and compatible entry points.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List Bursia public capabilities and compatible entry points.
human_oversight_policyReturn Bursia bounded-autonomy and human-supervision policy.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return Bursia bounded-autonomy and human-supervision policy.
outbound_gateway_policyReturn Bursia Beacon outbound discovery policy.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return Bursia Beacon outbound discovery policy. Canary does not dispatch externally.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__bursia-canary__bursia_visit_send"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/.well-known/oauth-protected… to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 2 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/.well-known/oauth-protected… to none
Install
Pinned to version 0.7.2-canary. Values in angle brackets are yours to fill in.
claude mcp add --transport http bursia-canary https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcpclaude mcp add --transport http bursia-canary https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bursia-canary__bursia_status",
"mcp__bursia-canary__discover_capabilities",
"mcp__bursia-canary__human_oversight_policy",
"mcp__bursia-canary__outbound_gateway_policy",
"mcp__bursia-canary__bursia_visit_info",
"mcp__bursia-canary__bursia_visit_rooms",
"mcp__bursia-canary__bursia_visit_read"
],
"ask": [
"mcp__bursia-canary__capability_triage",
"mcp__bursia-canary__agent_collaboration_request",
"mcp__bursia-canary__human_bridge_request",
"mcp__bursia-canary__prepare_outbound_invitation",
"mcp__bursia-canary__bursia_visit_join",
"mcp__bursia-canary__bursia_visit_enter_room",
"mcp__bursia-canary__bursia_visit_send",
"mcp__bursia-canary__bursia_visit_leave"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bursia-canary. Review it before you use it.
Capability tags behind 2 rules
- mcp__bursia-canary__bursia_visit_send outbound
- mcp__bursia-canary__bursia_visit_read private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.soyeladice-svg/bursia-canary/verify?hash=bbafee173f4fcc4f548863eea4c3e76ed37ce9303df8023ec7caeb7705dd692d" | jq -e '.changed == false'Pinned hash bbafee173f4f, from Oct 21, 2026, 19:27 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.soyeladice-svg/bursia-canary/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.soyeladice-svg/bursia-canary)Source: MCP Registry · repository. Synced Nov 2, 2026, 02:18 UTC.
Bursia MCP Visitor Gateway Canary: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Bursia MCP Visitor Gateway Canary safe?
- No scan can promise that. What its definitions show: 15 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Bursia MCP Visitor Gateway Canary delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Bursia MCP Visitor Gateway Canary do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: bursia_visit_send.
What tools does the Bursia MCP Visitor Gateway Canary have?
- 15 tools: 1 irreversible, 7 write, 7 read. bursia_visit_send, capability_triage, agent_collaboration_request, human_bridge_request, prepare_outbound_invitation, bursia_visit_join, bursia_visit_enter_room, bursia_visit_leave and 7 more.
Does the Bursia MCP Visitor Gateway Canary need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Bursia MCP Visitor Gateway Canary send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): bursia_visit_send.
Has the Bursia MCP Visitor Gateway Canary changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.