pawpulse
https://pawpulse.dougalpaw.workers.dev
Registry code: 13cfc0055ab026a4
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.
- endpoint
- https://pawpulse.dougalpaw.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is pawpulse live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is pawpulse free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pawpulse have?
- 6 tools: list_heartbeats, get_status, create_monitor, update_monitor, delete_monitor, setup_instructions.
- Is pawpulse safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_heartbeats unknown 1h ago
List recent heartbeats for a monitor (newest first). Private monitors require manage_token.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" }, "limit": { "type": "number", "description": "1-500, default 50." }, "manage_token": { "type": "string", "description": "The monitor's manage_token (returned once by create_monitor)." } } }arguments 19 linesget_status unknown 1h ago
Get the current status of a monitor. Private monitors require manage_token.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" }, "manage_token": { "type": "string", "description": "The monitor's manage_token (returned once by create_monitor)." } } }arguments 15 linescreate_monitor unknown never probed
Create a new anonymous Paw Pulse monitor. Returns ingest_token and manage_token exactly once — store them, they cannot be recovered.
{ "type": "object", "properties": { "name": { "type": "string", "description": "Display name, not treated as identifying." }, "public": { "type": "boolean", "description": "Whether /v1/monitors/:id/status and /s/:id are public." }, "webhook_url": { "type": "string", "description": "Optional https:// webhook for alerts." }, "grace_seconds": { "type": "number", "description": "60-86400, default 300." }, "slow_tps_threshold": { "type": "number", "description": "Optional tokens/sec floor." } } }arguments 25 linesupdate_monitor unknown never probed
Change a monitor's name, grace period, slow threshold, webhook or visibility. Only the fields you pass change.
{ "type": "object", "required": [ "id", "manage_token" ], "properties": { "id": { "type": "string" }, "name": { "type": "string" }, "public": { "type": "boolean" }, "webhook_url": { "type": [ "string", "null" ], "description": "https:// webhook, or null to clear." }, "manage_token": { "type": "string", "description": "The monitor's manage_token (returned once by create_monitor)." }, "grace_seconds": { "type": "number", "description": "60-86400." }, "slow_tps_threshold": { "type": [ "number", "null" ], "description": "Tokens/sec floor, or null to clear." } } }arguments 40 linesdelete_monitor unknown never probed
Permanently delete a monitor and all its heartbeats. Cannot be undone.
{ "type": "object", "required": [ "id", "manage_token" ], "properties": { "id": { "type": "string" }, "manage_token": { "type": "string", "description": "The monitor's manage_token (returned once by create_monitor)." } } }arguments 16 linessetup_instructions unknown never probed
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.
{ "type": "object", "required": [ "id", "ingest_token" ], "properties": { "id": { "type": "string" }, "llm_kind": { "enum": [ "ollama", "openai", "none" ], "type": "string", "description": "none = plain heartbeat, no LLM probe. Default ollama." }, "ingest_token": { "type": "string" } } }arguments 24 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id13cfc0055ab026a4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/13cfc0055ab026a4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/13cfc0055ab026a4?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.