Home / MCP registry index / dev.workers.dougalpaw.pawpulse/pawpulse
Paw Pulse
dev.workers.dougalpaw.pawpulse/pawpulse in the official MCP registry.
Endpoint https://pawpulse.dougalpaw.workers.dev/mcp. Source: github.com/dougal-paw/pawpulse.
The registry describes it as: Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
We read its 6 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
create_monitor get_status list_heartbeats update_monitor delete_monitor setup_instructions
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-workers-dougalpaw-pawpulse-pawpulse)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.