Paw Pulse MCP server
dev.workers.dougalpaw.pawpulse/pawpulsepawpulse.dougalpaw.workers.devstreamable-httpv0.3.0Scanned
Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
6 tools: 1 can delete or cancel things, 1 do something that can't be undone, 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Paw Pulse MCP server can do
The Paw Pulse MCP server is published by pawpulse.dougalpaw.workers.dev, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: delete_monitor), do things that cannot be undone, such as sending, paying or publishing (create_monitor) and create or change data (2 tools: update_monitor and setup_instructions). 2 tools only read.
2 tools can send data out of your system (create_monitor and update_monitor).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Deletes or cancels 1Claude Code: deny
delete_monitorPermanently delete a monitor and all its heartbeats.No findings
Why it is in this group
- The name "delete_monitor" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently delete a monitor and all its heartbeats. Cannot be undone.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 1Claude Code: ask
create_monitorCreate a new anonymous Paw Pulse monitor.Can send data outNo findings
Why it is in this group
- The name "create_monitor" says "create": a word for a change.
- The description says "cannot be recovered".
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Create a new anonymous Paw Pulse monitor. Returns ingest_token and manage_token exactly once — store them, they cannot be recovered.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
setup_instructionsShell commands to install the heartbeat script on the box being monitored and run it from cron.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
update_monitorChange a monitor's name, grace period, slow threshold, webhook or visibility.Can send data outNo findings
Why it is in this group
- The name "update_monitor" says "update": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Change a monitor's name, grace period, slow threshold, webhook or visibility. Only the fields you pass change.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_statusGet the current status of a monitor.No findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
Description, as the server wrote it Get the current status of a monitor. Private monitors require manage_token.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_heartbeatsList recent heartbeats for a monitor (newest first).No findings
Why it is in this group
- The name "list_heartbeats" says "list": a word for reading.
Description, as the server wrote it List recent heartbeats for a monitor (newest first). Private monitors require manage_token.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pawpulse.dougalpaw.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including delete_monitor (destructive), create_monitor (irreversible), update_monitor (write), setup_instructions (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:create_monitorCan't be undoneinputSchema
- Changed:update_monitorChanges thingsinputSchema
Tools2 changed.~2 changedView diff
- Changed:create_monitorCan't be undoneinputSchema
- Changed:update_monitorChanges thingsinputSchema
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pawpulse https://pawpulse.dougalpaw.workers.dev/mcpclaude mcp add --transport http pawpulse https://pawpulse.dougalpaw.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pawpulse__get_status",
"mcp__pawpulse__list_heartbeats"
],
"ask": [
"mcp__pawpulse__create_monitor",
"mcp__pawpulse__update_monitor",
"mcp__pawpulse__setup_instructions"
],
"deny": [
"mcp__pawpulse__delete_monitor"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pawpulse. Review it before you use it.
Capability tags behind 2 rules
- mcp__pawpulse__create_monitor outbound
- mcp__pawpulse__update_monitor outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.dougalpaw.pawpulse/pawpulse/verify?hash=4c4fe773d8a3d716201cf8b942cb629636aec983d5952cbc4ed98f9ae837e41a" | jq -e '.changed == false'Pinned hash 4c4fe773d8a3, from Nov 11, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.dougalpaw.pawpulse/pawpulse/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.dougalpaw.pawpulse/pawpulse)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
Paw Pulse MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Paw Pulse MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Paw Pulse MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_monitor.
Can the Paw Pulse MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_monitor.
What tools does the Paw Pulse MCP server have?
- 6 tools: 1 destructive, 1 irreversible, 2 write, 2 read. delete_monitor, create_monitor, update_monitor, setup_instructions, get_status and list_heartbeats.
Does the Paw Pulse MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Paw Pulse MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_monitor and update_monitor.
Has the Paw Pulse MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.