Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Paw Pulse

REMOTE · PULSE.DOUGALPAW.COM

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

60 Trust /100

Last scanned (20 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 615 tokens (~87/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Oct 26 +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.

  • 21 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 20 Oct 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Oct 2026 · Probed https://pulse.dougalpaw.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dougalpaw.com CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 d1e55eed8ee6ec981349207b2db600ff
SANs: dougalpaw.com, pulse.dougalpaw.com, *.pulse.dougalpaw.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pulse.dougalpaw.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
dougalpaw.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pulse.dougalpaw.com/mcp Verified 200
http (plaintext) http://pulse.dougalpaw.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~530 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_monitor ~116

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

NameTypeReqDescription
grace_secondsnumber–60-86400, default 300.
namestring–Display name, not treated as identifying.
publicboolean–Whether /v1/monitors/:id/status and /s/:id are public.
slow_tps_thresholdnumber–Optional tokens/sec floor.
webhook_urlstring–Optional https:// webhook for alerts.

No output schema declared.

No examples provided.

delete_monitor ~57

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

NameTypeReqDescription
idstringyesMonitor id, as returned by create_monitor.
manage_tokenstringyesThe monitor's manage_token (returned once by create_monitor).

No output schema declared.

No examples provided.

get_status ~56

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

NameTypeReqDescription
idstringyesMonitor id, as returned by create_monitor.
manage_tokenstring–The monitor's manage_token (returned once by create_monitor).

No output schema declared.

No examples provided.

list_heartbeats ~77

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

NameTypeReqDescription
idstringyesMonitor id, as returned by create_monitor.
limitnumber–1-500, default 50.
manage_tokenstring–The monitor's manage_token (returned once by create_monitor).

No output schema declared.

No examples provided.

setup_instructions ~93

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.

NameTypeReqDescription
idstringyesMonitor id, as returned by create_monitor.
ingest_tokenstringyesThe monitor's ingest_token (returned once by create_monitor).
llm_kindstring–none = plain heartbeat, no LLM probe. Default ollama.

No output schema declared.

No examples provided.

update_monitor ~131

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

NameTypeReqDescription
grace_secondsnumber–60-86400.
idstringyesMonitor id, as returned by create_monitor.
manage_tokenstringyesThe monitor's manage_token (returned once by create_monitor).
namestring–New display name.
publicboolean––
slow_tps_thresholdnumber|null–Tokens/sec floor, or null to clear.
webhook_urlstring|null–https:// webhook, or null to clear.

No output schema declared.

No examples provided.

Install

How do I install the Paw Pulse MCP server?

Paw Pulse is a hosted endpoint at https://pulse.dougalpaw.com/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.

remote · pulse.dougalpaw.com

# add to Claude Code
claude mcp add --transport http com-dougalpaw-pawpulse 'https://pulse.dougalpaw.com/mcp'
Common questions

What is the Paw Pulse MCP server?

Paw Pulse is an MCP server listed in the public MCP registry as com.dougalpaw/pawpulse. Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts. This page covers its hosted endpoint (https://pulse.dougalpaw.com/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 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.