Remote MCP · Endpoint
com.sibfly/ground-motion MCP server
No. com.sibfly/ground-motion answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://sibfly.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.sibfly/ground-motion
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 242 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Measured ground motion per US address (NASA InSAR). Self-register, $0.40/report, misses free.
- Website
- https://sibfly.com/
- Repository
- https://github.com/james-sib/sibfly-api
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 242 ms |
| 1 day ago | Handshake completed | 189 ms |
| 3 days ago | Handshake completed | 181 ms |
| 3 days ago | Handshake completed | 162 ms |
| 4 days ago | Handshake completed | 174 ms |
| 5 days ago | Handshake completed | 233 ms |
| 7 days ago | Handshake completed | 177 ms |
| 10 days ago | Handshake completed | 236 ms |
| 12 days ago | Handshake completed | 211 ms |
| 15 days ago | Handshake completed | 264 ms |
| 17 days ago | Handshake completed | 265 ms |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Handshake completed | 268 ms |
| 23 days ago | Handshake completed | 238 ms |
| 25 days ago | Handshake completed | 209 ms |
| 26 days ago | Handshake completed | 228 ms |
| 28 days ago | Handshake completed | 253 ms |
| 29 days ago | Handshake completed | 241 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.
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 com.sibfly/ground-motion and makes no claim about it beyond what these checks measured.