Experimental MCP checks: synthetic tests and live HTTP history for a Guardian-owned service.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Run a controlled synthetic health check and store its result. NOT an external service probe.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http agent-guardian https://agent-guardian.saromy-export.workers.dev/mcp
Run a controlled synthetic health check and store its result. NOT an external service probe.
| Argument |
|---|
| Type |
|---|
| Description |
|---|
| scenario* | string |
{
"type": "object",
"required": [
"scenario"
],
"properties": {
"scenario": {
"enum": [
"healthy",
"malformed",
"unavailable"
],
"type": "string"
}
},
"additionalProperties": false
}Perform a real HTTP check ONLY against Guardian's own fixed test target. Globally rate-limited to one check per minute. Not third-party monitoring.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}Read measured synthetic check history over the last 24 hours. NOT independent uptime monitoring.
| Argument | Type | Description |
|---|---|---|
| scenario | string |
{
"type": "object",
"properties": {
"scenario": {
"enum": [
"healthy",
"malformed",
"unavailable"
],
"type": "string"
}
},
"additionalProperties": false
}Read real HTTP observations of Guardian's own test target from the last 24 hours, including sample size, availability, and latency.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 15, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.