mcpbeat Sign in

Agent Health MCP Server

answering

Agent Health is answering right now. Last checked 11 min ago. It exposes 11 tools.

Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.

Uptime history 15 hours of history
15 hours agonow
100.0%
Uptime 24h
56 of 56 checks
11
Tools
read from the server
408 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Agent Health every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add agent-health --transport http https://autonet.work/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-health": {
      "url": "https://autonet.work/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-health]
url = "https://autonet.work/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-health": {
      "url": "https://autonet.work/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-health": {
      "url": "https://autonet.work/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
agent_domain_challenge
Issue/retrieve a DNS TXT challenge for your agent's exact endpoint hostname. Owner key required. Publish the returned name/value in your DNS, then call verify_agent_domain. Pending challenges expire in 24 hours.
agent_endpoint_assessment
With consent=true run two bounded HEAD/GET checks on your DNS-verified endpoint, max once/hour. With consent=false read your last private result. Not an audit or LLM test; no score effect.
agent_health_checks
Read recent HTTP/TLS results to diagnose failures. Limit 1–500.
agent_health_heartbeat
Send an owner-authenticated heartbeat from the actual worker loop; does not replace endpoint checks. Use the agent-specific key, not X-Autonet-Token. Never send a heartbeat to pretend a failed worker is alive.
agent_health_instructions
Read FIRST: purpose, endpoint ownership requirements, heartbeat setup, scoring limits, API and free service usage.
agent_health_status
Read public operational status and nested trust score. Provisional score is null; not identity/safety certification.
agent_webhook_secret
Owner-only retrieve webhook signing secret, or rotate it when explicitly requested. Keep the secret private.
delete_agent_health
Permanently remove an owned registration and probe history when the operator requests it. Admin request logs retain up to 30 days.
update_agent_health
Owner-only update. Pause when retiring/testing; resume with paused=false. Endpoint and webhook must be public URLs you control.
register
register_agent_health
Register ONCE your own deployed public agent readiness endpoint; save the returned api_key securely. Read agent_health_instructions first. Never register example.com, a vendor homepage, or an unrelated service. Without your own public endpoint, do not register: heartbeat-only monitoring is unsupported. Use a cheap GET returning 2xx only when the agent can serve work. Intervals 30–3600 seconds. Enable heartbeats only if the worker will send them automatically. Name/endpoint/history are public.
verify
verify_agent_domain
Check your published DNS TXT record. Proves domain control only, not agent identity or safety. Checks limited to once per minute. Successful proof renews hourly while TXT remains, expiring after 24 hours without renewal.

Endpoints

URLTransportStateLatencyChecked
https://autonet.work/mcp streamable-http answering 377 ms 11 min ago

Alternatives to Agent Health

same job, measured the same way
UptyBots
by uptybots

Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

50 installs/wk 15 tools answering
Agent Domains
by clize

Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts.

1 824 installs/wk local only
Sentinel
by rootstuff

Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.

answering
D
Watchpup
by workers-watchpup-watchpup

Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.

12 tools answering
HostTracker
by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering
Uptimely
by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering
Uptimemonitoring
by uptimemonitoring

Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.

answering
C
Monitoring
by pingvera

Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.

answering

Agent Health — questions

Answers built from our own checks of this server.

What can Agent Health do?
It exposes 11 tools, read directly from the server on our last check. Among them: agent_domain_challenge, agent_endpoint_assessment, agent_health_checks, agent_health_heartbeat, agent_health_instructions, agent_health_status and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Health working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 56 of 56 checks got a reply (100.0%), average response time 408 ms. The bar chart above shows every period we have measured.
How do I connect Agent Health?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Health need an API key?
No. Agent Health completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Health?
It answers our handshake in 408 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.