Remote MCP · Endpoint

Paw Pulse MCP server

No. Paw Pulse answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pulse.dougalpaw.com/mcp

The last check completed an MCP handshake.

Registry name
com.dougalpaw/pawpulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
449 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
Listing
From the official MCP registry (active).
Recent checks of Paw Pulse
CheckedResultHandshake
1 hour agoHandshake completed449 ms
9 days agoHandshake completed71 ms
10 days agoHandshake completed107 ms
11 days agoHandshake completed55 ms
12 days agoHandshake completed47 ms
14 days agoHandshake completed54 ms
14 days agoHandshake completed68 ms
15 days agoHandshake completed91 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed81 ms
21 days agoHandshake completed93 ms
24 days agoHandshake completed72 ms
26 days agoHandshake completed75 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Paw Pulse and makes no claim about it beyond what these checks measured.