Pulse — heartbeat & status monitor for AI agents
Your agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http pulse-heartbeat-status-monitor-for-ai-ag 'https://pulse.notdown-app.workers.dev/mcp/{key}'
{
"mcpServers": {
"pulse-heartbeat-status-monitor-for-ai-ag": {
"type": "http",
"url": "https://pulse.notdown-app.workers.dev/mcp/{key}"
}
}
}
Frequently asked questions
What is Pulse — heartbeat & status monitor for AI agents?
Your agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call.
How do I install Pulse — heartbeat & status monitor for AI agents?
It runs as a remote server. In Claude Code: claude mcp add --transport http pulse-heartbeat-status-monitor-for-ai-ag 'https://pulse.notdown-app.workers.dev/mcp/{key}'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Pulse — heartbeat & status monitor for AI agents need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Who maintains Pulse — heartbeat & status monitor for AI agents?
It is published by dev.workers.notdown-app.pulse. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.