Remote MCP · Endpoint

DeskPulse MCP server

No. DeskPulse answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://deskpulse.mubado.cloud/mcp

The last check completed an MCP handshake.

Registry name
io.github.Abaddon-git/deskpulse
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
730 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paid MCP for Kraken + Hyperliquid book depth, funding and basis. x402 USDC on Base.
Listing
From the official MCP registry (active).
Recent checks of DeskPulse
CheckedResultHandshake
3 hours agoHandshake completed730 ms
9 days agoHandshake completed691 ms
10 days agoHandshake completed693 ms
11 days agoHandshake completed683 ms
12 days agoHandshake completed692 ms
14 days agoHandshake completed698 ms
14 days agoHandshake completed688 ms
15 days agoHandshake completed765 ms
17 days agoHandshake completed694 ms
19 days agoHandshake completed692 ms
21 days agoHandshake completed902 ms
24 days agoHandshake completed704 ms
26 days agoHandshake completed718 ms
28 days agoHandshake completed705 ms

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

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 DeskPulse and makes no claim about it beyond what these checks measured.