Remote MCP · Endpoint

NAIF Gravity MCP server

No. NAIF Gravity answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://naifgravity.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.naief9961-tech/naif-fixgraph
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
518 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free MCP/API diagnostics. Micro Tools V2: free preview, $1 JSON check, $2 API shape, $3 normalize.
Listing
From the official MCP registry (active).
Recent checks of NAIF Gravity
CheckedResultHandshake
1 hour agoHandshake completed518 ms
1 day agoHandshake completed461 ms
3 days agoHandshake completed462 ms
6 days agoHandshake completed157 ms
8 days agoHandshake completed448 ms
9 days agoHandshake completed518 ms
11 days agoHandshake completed472 ms
11 days agoHandshake completed484 ms
13 days agoHandshake completed470 ms
16 days agoHandshake completed517 ms
17 days agoHandshake completed491 ms
19 days agoHandshake completed507 ms
20 days agoHandshake completed506 ms
21 days agoHandshake completed476 ms
22 days agoHandshake completed463 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 NAIF Gravity and makes no claim about it beyond what these checks measured.