Remote MCP · Endpoint

SolidPing MCP server

No. SolidPing answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://solidping.io/api/v1/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
io.github.fclairamb/solidping
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
313 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
Listing
From the official MCP registry (active).
Recent checks of SolidPing
CheckedResultHandshake
1 hour agoHandshake completed313 ms
2 days agoHandshake completed292 ms
4 days agoHandshake completed298 ms
6 days agoHandshake completed276 ms
7 days agoHandshake completed260 ms
9 days agoHandshake completed273 ms
10 days agoHandshake completed267 ms
11 days agoHandshake completed289 ms
14 days agoHandshake completed263 ms
15 days agoHandshake completed275 ms
17 days agoHandshake completed268 ms
18 days agoHandshake completed277 ms
20 days agoHandshake completed293 ms
21 days agoHandshake completed265 ms
22 days agoHandshake completed270 ms

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