# Paw Pulse (remote · pawpulse.dougalpaw.workers.dev)

Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- remote · `pawpulse.dougalpaw.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-dougalpaw-pawpulse-pawpulse/pawpulse.md), [page](https://verifymcp.io/servers/dev-workers-dougalpaw-pawpulse-pawpulse/pawpulse)

## Channel facts

- Endpoint: `https://pawpulse.dougalpaw.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.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-10-19.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_monitor).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 615 tokens (~87/item across 7 items; 6 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Paw Pulse MCP server?

Paw Pulse is a hosted endpoint at https://pawpulse.dougalpaw.workers.dev/mcp, 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-dougalpaw-pawpulse-pawpulse 'https://pawpulse.dougalpaw.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-dougalpaw-pawpulse-pawpulse": {
      "url": "https://pawpulse.dougalpaw.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-dougalpaw-pawpulse-pawpulse": {
      "type": "http",
      "url": "https://pawpulse.dougalpaw.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-dougalpaw-pawpulse-pawpulse]
url = "https://pawpulse.dougalpaw.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-dougalpaw-pawpulse-pawpulse": {
      "type": "remote",
      "url": "https://pawpulse.dougalpaw.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-dougalpaw-pawpulse-pawpulse --url 'https://pawpulse.dougalpaw.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-dougalpaw-pawpulse-pawpulse:
    url: "https://pawpulse.dougalpaw.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-dougalpaw-pawpulse-pawpulse": {
      "Transport": "http",
      "Url": "https://pawpulse.dougalpaw.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-dougalpaw-pawpulse-pawpulse -t streamable-http -u 'https://pawpulse.dougalpaw.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-dougalpaw-pawpulse-pawpulse": {
      "type": "http",
      "url": "https://pawpulse.dougalpaw.workers.dev/mcp"
    }
  }
}
```

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-10-18 (score 60, +1)

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

### 2026-10-17 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 59)

First indexed and scored.

## MCP tools (6)

### `create_monitor` (~116 tokens)

Create monitor

Create a new anonymous Paw Pulse monitor. Returns ingest_token and manage_token exactly once — store them, they cannot be recovered.

Input parameters:

- `grace_seconds` (number): 60-86400, default 300.
- `name` (string): Display name, not treated as identifying.
- `public` (boolean): Whether /v1/monitors/:id/status and /s/:id are public.
- `slow_tps_threshold` (number): Optional tokens/sec floor.
- `webhook_url` (string): Optional https:// webhook for alerts.

### `get_status` (~56 tokens)

Get monitor status

Get the current status of a monitor. Private monitors require manage_token.

Input parameters:

- `id` (string, required): Monitor id, as returned by create_monitor.
- `manage_token` (string): The monitor's manage_token (returned once by create_monitor).

### `list_heartbeats` (~77 tokens)

List recent heartbeats

List recent heartbeats for a monitor (newest first). Private monitors require manage_token.

Input parameters:

- `id` (string, required): Monitor id, as returned by create_monitor.
- `limit` (number): 1-500, default 50.
- `manage_token` (string): The monitor's manage_token (returned once by create_monitor).

### `update_monitor` (~131 tokens)

Update monitor settings

Change a monitor's name, grace period, slow threshold, webhook or visibility. Only the fields you pass change.

Input parameters:

- `grace_seconds` (number): 60-86400.
- `id` (string, required): Monitor id, as returned by create_monitor.
- `manage_token` (string, required): The monitor's manage_token (returned once by create_monitor).
- `name` (string): New display name.
- `public` (boolean)
- `slow_tps_threshold` (number|null): Tokens/sec floor, or null to clear.
- `webhook_url` (string|null): https:// webhook, or null to clear.

### `delete_monitor` (~57 tokens)

Delete monitor

Permanently delete a monitor and all its heartbeats. Cannot be undone.

Input parameters:

- `id` (string, required): Monitor id, as returned by create_monitor.
- `manage_token` (string, required): The monitor's manage_token (returned once by create_monitor).

### `setup_instructions` (~93 tokens)

Get setup instructions

Shell commands to install the heartbeat script on the box being monitored and run it from cron. Pass the id and ingest_token from create_monitor.

Input parameters:

- `id` (string, required): Monitor id, as returned by create_monitor.
- `ingest_token` (string, required): The monitor's ingest_token (returned once by create_monitor).
- `llm_kind` (string): none = plain heartbeat, no LLM probe. Default ollama.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-dougalpaw-pawpulse-pawpulse/pawpulse#diagnostics

## Score history

- 2026-10-19: 60
- 2026-10-18: 60
- 2026-10-17: 59
- 2026-10-16: 59

## Common questions

### What is the Paw Pulse MCP server?

Paw Pulse is an MCP server listed in the public MCP registry as dev.workers.dougalpaw.pawpulse/pawpulse. Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts. This page covers its hosted endpoint (https://pawpulse.dougalpaw.workers.dev/mcp).

### Is the Paw Pulse MCP server safe to use?

Paw Pulse scores 60 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 Paw Pulse MCP server expose?

Paw Pulse exposes 6 tools: create_monitor, get_status, list_heartbeats, update_monitor, delete_monitor, setup_instructions. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.

### Does the Paw Pulse MCP server require authentication?

No. We connected to Paw Pulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Paw Pulse MCP server still maintained?

Paw Pulse is still listed as active in the MCP registry. We last reached this channel on 19 October 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://pawpulse.dougalpaw.workers.dev/mcp
- Repository: https://github.com/dougal-paw/pawpulse
- Website: https://pawpulse.dougalpaw.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-dougalpaw-pawpulse-pawpulse/pawpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-dougalpaw-pawpulse-pawpulse/pawpulse.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-dougalpaw-pawpulse-pawpulse/pawpulse
