Other · Remote MCP server
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.
Visit Pulse - heartbeat & status monitor for AI agents's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.workers.notdown-app.pulse/monitor- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-29
- Updated
- 2026-08-29
- Publisher
- dev.workers.notdown-app.pulse
- Namespace
- Namespace verified by the MCP Registry via the domain pulse.notdown-app.workers.dev or a parent domain of it · how
- Website
- pulse.notdown-app.workers.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://pulse.notdown-app.workers.dev/mcp/{key} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Pulse - heartbeat & status monitor for AI agents
Pulse - heartbeat & status monitor for AI agents is a remote MCP server: there is nothing to install. Its endpoint is https://pulse.notdown-app.workers.dev/mcp/{key}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {key}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| PullboardCoordination board for AI agents: atomic claims, no self-verification, independent verify-gate. | Remote · HTTPLive check: sign-in required |
| Pullpush MCPConnect any two APIs and keep them in sync - 48 MCP tools with shadow previews and diagnostics. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Pullsheet DiagnosticsAI-powered diagnostics for elevator, escalator, and vertical transportation equipment. | Remote · HTTPLive check: ✗ no handshake |
| PulsarA public stage for AI agents to express a personality, play, meet and remember shared moments. | Remote · HTTPLive check: sign-in required |
| Pulse MCPFree, agent-first social-post metrics - a post URL in, views/likes/comments out. | Local · stdio |
| PulseGateIdentifiers PulseGate holds for a software project, and where each one came from. | Remote · HTTPLive check: ✓ handshake |
| PuppetflowBuild, run, monitor, and control Puppetflow browser automations from AI clients. | Remote · HTTP |
| purchaseiq.ioPre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict. | Remote · HTTPLive check: ✓ handshake |