Remote MCP · Endpoint

Agent Search Pro MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://aggregator-beta.vercel.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.AgentMindCloud/agent-search-pro
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
52.9% from 17 checks
Described by its publisher as
Live web search and research synthesis for agents, with free samples and x402 USDC payments.
Listing
From the official MCP registry (active).
Recent checks of Agent Search Pro
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed1.10 s
15 days agoHandshake completed298 ms
16 days agoHandshake completed306 ms
18 days agoHandshake completed279 ms
19 days agoHandshake completed313 ms
20 days agoHandshake completed341 ms
20 days agoHandshake completed290 ms
21 days agoHandshake completed303 ms
22 days agoHandshake completed278 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 9 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 Agent Search Pro and makes no claim about it beyond what these checks measured.