Developer · Remote MCP server
Agentmonitorrelay MCP
AI agent run monitoring with incident replay and SLA receipts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.clauxel.agentmonitorrelay/agentmonitorrelay-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-19
- Updated
- 2026-05-19
- Publisher
- com.clauxel.agentmonitorrelay
- Namespace
- Namespace verified by the MCP Registry via the domain agentmonitorrelay.clauxel.com or a parent domain of it · how
- Repository
- github.com/clauxel/agent-monitor-relay-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentmonitorrelay.clauxel.com/mcp | Authorization |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
How to connect Agentmonitorrelay MCP
Agentmonitorrelay MCP is a remote MCP server: there is nothing to install. Its endpoint is https://agentmonitorrelay.clauxel.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization. Clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| agentmark-ai MCP-SERVERInspect AgentMark traces and drive AgentMark Cloud: apps, experiments, metrics, deployments. | Local · stdio |
| agentmemGoverned memory for coding agents. Trust lifecycle, conflict detection, health scoring. | Local · stdio |
| Agentmemorymcp MCPA paid remote MCP for agent memory MCP, built to return verdicts, receipts, usage logs, and audit-re. | Remote · HTTPLive check: ✗ no handshake |
| AgentmetalRent a Linux VPS from an AI agent: provision, SSH in, run commands. Pay USDC (x402) or card. | Local · stdio |
| AgentoolRankSearch, compare and list 460+ open-source AI agent tools ranked by live GitHub activity. | Remote · HTTPLive check: ✗ no handshake |
| AgentPay Domain & Network LookupPay-per-call DNS, WHOIS/RDAP, IP and domain reports for agents. x402 USDC on Base or Algorand. | Remote · HTTPLive check: ✓ handshake |
| agentpcInstant, resettable Windows, Ubuntu and Arch Linux ARM desktop VMs for AI agents on Apple Silicon. | Local · stdio |
| AgentPingProduction observability for AI agents: search runs, read evaluations, acknowledge incidents. | Remote · HTTPLive check: sign-in required |