Remote MCP · Endpoint

HasData DuckDuckGo MCP server

No. HasData DuckDuckGo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.hasdata.com/mcp?apis=duckduckgo

The last check completed an MCP handshake.

Registry name
com.hasdata/duckduckgo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
DuckDuckGo search as JSON. Ranked results, ads in their own array, 37 regions.
Listing
From the official MCP registry (active).
Recent checks of HasData DuckDuckGo
CheckedResultHandshake
1 hour agoHandshake completed151 ms
2 days agoHandshake completed122 ms
4 days agoHandshake completed130 ms
5 days agoHandshake completed134 ms
7 days agoHandshake completed122 ms
8 days agoHandshake completed130 ms
9 days agoHandshake completed169 ms
12 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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