Remote MCP · Endpoint

No Niner Data Tools MCP server

No. No Niner Data Tools answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://noniner.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.fredxhansson-cmyk/noniner
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
80 ms
Tools exposed
95 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
No-code web scraping & data-extraction Apify actors: scrape and enrich web data at scale.
Listing
From the official MCP registry (active).
Recent checks of No Niner Data Tools
CheckedResultHandshake
34 minutes agoHandshake completed80 ms
9 days agoHandshake completed77 ms
10 days agoHandshake completed98 ms
11 days agoHandshake completed128 ms
12 days agoHandshake completed1.24 s
14 days agoHandshake completed216 ms
14 days agoHandshake completed84 ms
15 days agoHandshake completed149 ms
17 days agoHandshake completed104 ms
19 days agoHandshake completed206 ms
21 days agoHandshake completed64 ms
24 days agoHandshake completed77 ms
26 days agoHandshake completed78 ms
28 days agoHandshake completed68 ms

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

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 No Niner Data Tools and makes no claim about it beyond what these checks measured.