DevOps
dougalpaw.com
An uptime and heartbeat monitoring service for creating, checking, updating, and deleting anonymous Paw Pulse monitors.
ENDPOINT 1
https://pulse.dougalpaw.com/mcp
MCP server metadata
- Name
- pawpulse
- Version
- 0.3.0
Paw Pulse monitors self-hosted LLM boxes (and any box with LLM_KIND=none) with outbound heartbeats. Typical flow: create_monitor -> setup_instructions -> run the commands on the box -> get_status. Store manage_token safely; it cannot be recovered.
Known tools 6
update_monitorChange a monitor's name, grace period, slow threshold, webhook or visibility.
Inferred read-onlysetup_instructionsShell commands to install the heartbeat script on the box being monitored and run it from cron.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pawpulse]
url = "https://pulse.dougalpaw.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pawpulse": {
"type": "http",
"url": "https://pulse.dougalpaw.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pawpulse
Remote MCP URL: https://pulse.dougalpaw.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pawpulse": {
"url": "https://pulse.dougalpaw.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pawpulse": {
"type": "http",
"url": "https://pulse.dougalpaw.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pawpulse",
"transport": "streamable-http",
"url": "https://pulse.dougalpaw.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.