# Pulse — heartbeat & status monitor for AI agents (remote · pulse.notdown-app.workers.dev)

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

- Trust score: 0/100 (low)
- Change this week: −69
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `pulse.notdown-app.workers.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-notdown-app-pulse-monitor/mcp-key.md), [page](https://verifymcp.io/servers/dev-workers-notdown-app-pulse-monitor/mcp-key)

## Channel facts

- Endpoint: `https://pulse.notdown-app.workers.dev/mcp/{key}`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 0/100
  - TLS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - Authorisation not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - HTTPS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - HSTS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - DNSSEC not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
- **Transport & Reachability**: 0/100
  - Transport not yet verified: the listed URL is a template whose key variable has no value or default, so there is no address for us to connect to.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 7 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Pulse — heartbeat & status monitor for AI agents MCP server?

Pulse — heartbeat & status monitor for AI agents is a hosted endpoint at https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-workers-notdown-app-pulse-monitor 'https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-pulse-monitor": {
      "url": "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-notdown-app-pulse-monitor": {
      "type": "http",
      "url": "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-notdown-app-pulse-monitor]
url = "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-notdown-app-pulse-monitor": {
      "type": "remote",
      "url": "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-notdown-app-pulse-monitor --url 'https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-notdown-app-pulse-monitor:
    url: "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-notdown-app-pulse-monitor": {
      "Transport": "http",
      "Url": "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-notdown-app-pulse-monitor -t streamable-http -u 'https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-pulse-monitor": {
      "type": "http",
      "url": "https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 0, −72)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `ping` (~262 tokens)

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.

Input parameters:

- `check` (string, required): A stable name for this job/agent, e.g. "nightly-sync" or "my-agent". Reuse the same name every run — that's how heartbeats accumulate. Created on first ping.
- `grace` (number): Optional: extra seconds of slack before a missed ping counts as down (default 20% of period).
- `note` (string): Optional one-line status note shown on the public page, e.g. "processed 240 rows" or "all green".
- `period` (number): Optional: how often you expect to ping, in seconds (default 3600 = hourly). If no ping arrives within period+grace, status becomes late/down.

### `list_checks` (~37 tokens)

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

### `get_check` (~38 tokens)

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

Input parameters:

- `check` (string, required): The check name (or its id).

### `delete_check` (~27 tokens)

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

Input parameters:

- `check` (string, required)

## Diagnostics

Captured diagnostic sections: Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-notdown-app-pulse-monitor/mcp-key#diagnostics

## Score history

- 2026-09-28: 0
- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59

## Common questions

### What is the Pulse — heartbeat & status monitor for AI agents MCP server?

Pulse — heartbeat & status monitor for AI agents is an MCP server listed in the public MCP registry as dev.workers.notdown-app.pulse/monitor. Your agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call. This page covers its hosted endpoint (https://pulse.notdown-app.workers.dev/mcp/{key}).

### Is the Pulse — heartbeat & status monitor for AI agents MCP server safe to use?

Pulse — heartbeat & status monitor for AI agents scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Pulse — heartbeat & status monitor for AI agents MCP server expose?

Pulse — heartbeat & status monitor for AI agents exposes 4 tools: ping, list_checks, get_check, delete_check. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.

### Does the Pulse — heartbeat & status monitor for AI agents MCP server require authentication?

Its publisher declares no required credentials for Pulse — heartbeat & status monitor for AI agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Pulse — heartbeat & status monitor for AI agents MCP server still maintained?

Pulse — heartbeat & status monitor for AI agents is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pulse.notdown-app.workers.dev/mcp/%7Bkey%7D
- Website: https://pulse.notdown-app.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-notdown-app-pulse-monitor/mcp-key.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-notdown-app-pulse-monitor/mcp-key.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-notdown-app-pulse-monitor/mcp-key