Remote MCP · Endpoint

HasData MCP server

No. HasData answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.hasdata.com/mcp

The last check completed an MCP handshake.

Registry name
com.hasdata/hasdata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.16 s
Tools exposed
68 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
Listing
From the official MCP registry (active).
Recent checks of HasData
CheckedResultHandshake
1 hour agoHandshake completed1.16 s
2 days agoHandshake completed884 ms
4 days agoHandshake completed172 ms
6 days agoHandshake completed889 ms
7 days agoHandshake completed137 ms
9 days agoHandshake completed79 ms
10 days agoHandshake completed130 ms
11 days agoHandshake completed217 ms
14 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—
22 days agoCredentials required—

The last 16 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 HasData and makes no claim about it beyond what these checks measured.