
Agentmonitorrelay Mcp
com.clauxel.agentmonitorrelayPublished by agentmonitorrelay.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026
AI agent run monitoring with incident replay and SLA receipts.
Overview
A paid remote MCP server for monitoring AI agent runs, detecting failures, replaying tool-call incidents and issuing SLA receipts.
- What you can do
- Record agent runs and their outcomes for tracking over time. Detect agent failures from recorded run data. Replay tool-call incidents to review what happened. Issue SLA receipts and export client status reports. All of this is done through a hosted remote endpoint rather than local tooling.
- When to use it
- Useful when you operate AI agents and want run history, failure detection, incident replay evidence and SLA reporting available to an assistant. It is a paid hosted service, so it suits teams that need ongoing monitoring rather than one-off checks.
- Requirements
- A remote Streamable HTTP MCP endpoint; no local package or runtime is needed. A paid plan chosen on the product website and a bearer token issued there, sent in the Authorization header. Network access to the hosted endpoint.
Installation
In SourceWeft
- Open Agentmonitorrelay Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.clauxel.agentmonitorrelay%2Fagentmonitorrelay-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"agentmonitorrelay": {
"type": "http",
"url": "https://agentmonitorrelay.clauxel.com/mcp"
}
}
}README
Agent Monitor Relay MCP
Track agent runs, failures, replay evidence, and SLA receipts from one MCP.
Paid remote MCP for AI agent run monitoring, failure detection, tool-call incident replay, SLA receipts, and client status exports.
Public Endpoints
- Website: https://agentmonitorrelay.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605
- MCP endpoint: https://agentmonitorrelay.clauxel.com/mcp
- Server card: https://agentmonitorrelay.clauxel.com/server-card.json
- Registry name:
com.clauxel.agentmonitorrelay/agentmonitorrelay-mcp
Access
This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.
Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.
Tools
record_agent_rundetect_agent_failurereplay_tool_call_incidentissue_sla_receiptexport_client_status
Quick Start
- Open the website and choose a plan.
- Create or request an API token.
- Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
- Send JSON-RPC requests with the bearer token.
Useful Links
- Product page: https://agentmonitorrelay.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605
- Pricing: https://agentmonitorrelay.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605#pricing
- Server card: https://agentmonitorrelay.clauxel.com/server-card.json
- MCP endpoint: https://agentmonitorrelay.clauxel.com/mcp
Status
This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.
Source: README.md at commit ef47bf1
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.