Skip to main content
Glama

Bursia MCP Visitor Gateway Canary

Server Details

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

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

B3.1/5.0

Scored across 15 tools

Disambiguation3/5

Most tools are clearly scoped, especially the bursia_visit_* session lifecycle, but the three prepare-only tools (agent_collaboration_request, human_bridge_request, prepare_outbound_invitation) and the overlapping status/policy tools create some ambiguity. Descriptions clarify recipient and policy context, but an agent could still hesitate between similar 'prepare but do not send' actions.

Naming Consistency3/5

The bursia_visit_* tools follow a consistent prefix+verb pattern, but the rest of the set mixes noun-based names (discover_capabilities, capability_triage, human_oversight_policy) with verb-noun names (prepare_outbound_invitation) and odd one-off forms (bursia_status). All names are readable and snake_case, but there is no single predictable convention across the server.

Tool Count4/5

Fifteen tools is at the upper edge of the typical well-scoped range and each major area (visitor lounge, policy, capability discovery, preparation) has representation. The count feels slightly heavy because several tools return policy/status information or prepare requests rather than performing distinct actions, but it is not bloated.

Completeness4/5

The visitor lounge lifecycle is well covered with join/enter/leave/rooms/read/send/info, and the canary's intentional no-dispatch stance is reflected in prepare-only outbound tools. Minor gaps remain around managing prepared requests or canceling/updating them, but agents can work around these and the core domain is covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      F
      maintenance
      A governed MCP server exposing 37 risk-checked tools with signed Ed25519 receipts on a Bitcoin-anchored ledger, failing closed if governance or receipt writing fails.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP tools over an AgentFox control plane: agents found in a codebase, the tools and MCP servers each can reach, security findings, policy linting and simulation, and audit verification. 25 tools, none changing enforcement; implemented in src/agentfox/apps/mcp_server.py as JSON-RPC 2.0 over stdio on the standard library, with no MCP SDK dependency.
      227 PyPI
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server lets agents inspect every Model Context Protocol server on the machine, verify tools by running them in a sandbox, and check each call against a human-approved baseline so that changed or newly appeared tools are blocked before they execute. It also surfaces token cost, capability facts, and drift history for each tool entirely locally, without uploading inventory or requiring an account.
      710 PyPI
      1
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources