Remote MCP · Endpoint
Nifra docs MCP server
No. Nifra docs answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 427 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 17 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 |
|---|---|---|
| 2 hours ago | Handshake completed | 427 ms |
| 2 days ago | Handshake completed | 431 ms |
| 4 days ago | Handshake completed | 404 ms |
| 5 days ago | Handshake completed | 402 ms |
| 7 days ago | Handshake completed | 467 ms |
| 8 days ago | Handshake completed | 429 ms |
| 9 days ago | Handshake completed | 398 ms |
| 12 days ago | Handshake completed | 335 ms |
| 13 days ago | Handshake completed | 364 ms |
| 15 days ago | Handshake completed | 324 ms |
| 17 days ago | Handshake completed | 430 ms |
| 18 days ago | Handshake completed | 416 ms |
| 19 days ago | Handshake completed | 427 ms |
| 20 days ago | Handshake completed | 395 ms |
| 20 days ago | Handshake completed | 396 ms |
| 21 days ago | Handshake completed | 456 ms |
| 23 days ago | Handshake completed | 467 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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.