Remote MCP · Endpoint

Fuze Data Tools MCP server

No. Fuze Data Tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://datatools-hub.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.fredxhansson-cmyk/fuze
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
329 ms
Tools exposed
95 tools
Uptime, last 30 days
100% from 15 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 Fuze Data Tools
CheckedResultHandshake
1 hour agoHandshake completed329 ms
22 hours agoHandshake completed283 ms
2 days agoHandshake completed250 ms
3 days agoHandshake completed223 ms
4 days agoHandshake completed200 ms
5 days agoHandshake completed298 ms
6 days agoHandshake completed272 ms
8 days agoHandshake completed451 ms
11 days agoHandshake completed178 ms
13 days agoHandshake completed196 ms
15 days agoHandshake completed196 ms
18 days agoHandshake completed210 ms
20 days agoHandshake completed750 ms
22 days agoHandshake completed234 ms
24 days agoHandshake completed74 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 Fuze Data Tools and makes no claim about it beyond what these checks measured.