Pulse — heartbeat & status monitor for AI agents MCP Server

by workers-notdown-app-pulse Your server? Claim it

answering

Pulse — heartbeat & status monitor for AI agents is answering right now. Last checked 12 min ago. It exposes 4 tools.

Your agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call.

Uptime history 48 days of history · worst day 77%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

197 ms

Response time

average over 24h

open, no key

Access

streamable-http

Pulse — heartbeat & status monitor for AI agents missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add monitor --transport http https://pulse.notdown-app.workers.dev/mcp/{key}

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "monitor": {
      "url": "https://pulse.notdown-app.workers.dev/mcp/{key}"
    }
  }
}

~/.codex/config.toml

[mcp_servers.monitor]
url = "https://pulse.notdown-app.workers.dev/mcp/{key}"

.cursor/mcp.json

{
  "mcpServers": {
    "monitor": {
      "url": "https://pulse.notdown-app.workers.dev/mcp/{key}"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "monitor": {
      "url": "https://pulse.notdown-app.workers.dev/mcp/{key}"
    }
  }
}

Available tools 4

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

checks

list_checks

List all your checks with their current status (up/late/down/pending), last-seen time, ping count, and public status URL.

delete

delete_check

Delete a check and its history, by name or id.

get

get_check

Get one check's current status plus its recent ping history (timestamps and notes).

ping

ping

Send a heartbeat for a named check — call this once per run of your job/agent. If the named check doesn't exist yet it is created automatically (zero setup), so you can just ping the same name every run. Attach an optional one-line `note` (e.g. what the run did) that shows on the public status page. If a ping doesn't arrive within the expected period + grace, the check flips to 'late' then 'down' on its public status page. Returns the check's status and its public status_url.

Endpoints

URL	Transport	State	Latency	Checked
https://pulse.notdown-app.workers.dev/mcp/{key}	streamable-http	answering	234 ms	12 min ago

Alternatives to Pulse — heartbeat & status monitor for AI agents

same job, measured the same way

Pingcheck MCP

by churman1113

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

46 installs/wk local only

Uptimepage

by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

39 tools answering

Agent Domains

by clize

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

178 installs/wk local only

SolidPing

by fclairamb

Self-hostable uptime monitoring: create checks, read incidents, manage status pages.

answering

Fettle

by fettle

Uptime monitoring for developers — monitors, incidents, heartbeats, maintenance, status pages

375 installs/wk 49 tools answering

agent-check

by basenull

Process monitoring for AI agents: start runs, submit per-task evidence, complete runs.

answering

Orbilo

by orbilo

Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.

5 tools answering

Better Stack MCP by usefulapi

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

Pulse — heartbeat & status monitor for AI agents — questions

Answers built from our own checks of this server.

What can Pulse — heartbeat & status monitor for AI agents do?

It exposes 4 tools, read directly from the server on our last check. Among them: delete_check, get_check, list_checks, ping. 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 Pulse — heartbeat & status monitor for AI agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 197 ms. The bar chart above shows every period we have measured.

How do I connect Pulse — heartbeat & status monitor for AI agents?

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 Pulse — heartbeat & status monitor for AI agents need an API key?

No. Pulse — heartbeat & status monitor for AI agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Pulse — heartbeat & status monitor for AI agents?

It answers our handshake in 197 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.