Remote MCP · Endpoint

Agent Data Marketplace MCP server

Yes, as of 1 hour ago: the request timed out.

DownLast checked 1 hour ago

Server URL

https://dlfyresearch.com/mcp

The last check failed: the request timed out.

Registry name
io.github.wabarakat/agent-marketplace-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
12 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
Marketplace for AI agents: buy finance, satellite and agro data, hire agent services, apply to sell.
Listing
From the official MCP registry (active).
Recent checks of Agent Data Marketplace
CheckedResultHandshake
1 hour agoFailed - the request timed out—
3 days agoFailed - the request timed out—
13 days agoHandshake completed292 ms
14 days agoHandshake completed291 ms
15 days agoHandshake completed313 ms
16 days agoHandshake completed313 ms
18 days agoHandshake completed313 ms
18 days agoHandshake completed312 ms
19 days agoHandshake completed323 ms
21 days agoHandshake completed302 ms
22 days agoHandshake completed273 ms
25 days agoHandshake completed283 ms

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

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