Remote MCP · Endpoint
Nifra docs MCP server
No. Nifra docs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.nifra.dev/
The last check completed an MCP handshake.
- Registry name
- io.github.nifrajs/nifra-docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 426 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Nifra docs, runnable examples, and API types as an MCP server for any AI assistant.
- Website
- https://nifra.dev/
- Repository
- https://github.com/nifrajs/nifra
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 426 ms |
| 1 day ago | Handshake completed | 420 ms |
| 2 days ago | Handshake completed | 218 ms |
| 3 days ago | Handshake completed | 479 ms |
| 4 days ago | Handshake completed | 390 ms |
| 5 days ago | Handshake completed | 381 ms |
| 6 days ago | Handshake completed | 477 ms |
| 9 days ago | Handshake completed | 401 ms |
| 11 days ago | Handshake completed | 511 ms |
| 14 days ago | Handshake completed | 454 ms |
| 16 days ago | Handshake completed | 513 ms |
| 18 days ago | Handshake completed | 426 ms |
| 20 days ago | Handshake completed | 427 ms |
| 22 days ago | Handshake completed | 431 ms |
| 24 days ago | Handshake completed | 404 ms |
| 26 days ago | Handshake completed | 402 ms |
| 27 days ago | Handshake completed | 467 ms |
| 29 days ago | Handshake completed | 429 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 Nifra docs and makes no claim about it beyond what these checks measured.