agent-incident-relay-mcp
Server Details
Agent Incident Relay MCP — Article 73 5-clock broadcaster. One incident → simultaneous signed
Glama couldn't complete the latest health check. 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 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Server Listing
- Agent Incident Relay MCP
Related MCP Connectors
BFT Progress Council MCP — 5-voter Byzantine council halts agentic loops when no real progress is
Intelligence subscription protocol for AI agents. Scored, filtered AI intelligence signals via MCP.
Authenticated LLM MCP Agent
Related MCP Servers
- AlicenseAqualityCmaintenanceTamper-Evident Autonomous Agent Action Audit & Governance Logging MCP Server2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server enabling real-time communication, task delegation, and acknowledgment among multiple AI agents through a single local endpoint.28 npm4MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling evidence-driven multi-agent incident management with fault closure workflows, including diagnosis, approval, execution, verification, rollback, and audit-chain tracking.Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that lets multiple agent sessions (e.g., Claude Code, Claude Desktop) on the same machine communicate over shared channels like walkie-talkies, enabling them to exchange messages and coordinate tasks without any central broker.230 PyPI4MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.