Remote MCP · Endpoint

Feet per second to m/s, number discarded MCP server

No. Feet per second to m/s, number discarded answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/fps-ms/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/fps-ms
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
23 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Feet per second to m/s, number discarded
Listing
From the official MCP registry (active).
Recent checks of Feet per second to m/s, number discarded
CheckedResultHandshake
4 days agoHandshake completed23 ms
5 days agoHandshake completed27 ms
6 days agoHandshake completed14 ms
7 days agoHandshake completed43 ms
9 days agoHandshake completed48 ms
9 days agoHandshake completed17 ms
10 days agoHandshake completed23 ms
12 days agoHandshake completed38 ms
14 days agoHandshake completed44 ms
16 days agoHandshake completed46 ms
19 days agoHandshake completed31 ms
21 days agoHandshake completed14 ms
23 days agoHandshake completed22 ms
25 days agoHandshake completed15 ms
27 days agoHandshake completed39 ms
29 days agoHandshake completed16 ms
31 days agoHandshake completed15 ms
33 days agoHandshake completed36 ms

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

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 Feet per second to m/s, number discarded and makes no claim about it beyond what these checks measured.