https://api.anysearch.com/mcp ↗
Unified real-time search engine skill for AI agents.
AnySearch is a remote MCP server published at api.anysearch.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 611 ms, a delay an agent will notice. It offers a narrow, focused set of 4 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
batch_search — Description cut off mid-sentence ('or d')extract — Description ends abruptly ('answer the ')search — No explicit parameter constraints or error handling mentionedget_sub_domains — No inputSchema details for required parametersRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/anysearch-ai-anysearch)<a href="https://mcpmetrics.io/servers/anysearch-ai-anysearch"><img src="https://mcpmetrics.io/badge/anysearch-ai/anysearch/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 11:20:19 | Legacy | 200 | 647 | 200 | 659 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 200 | 617 | 200 | 610 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 200 | 420 | 200 | 254 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 200 | 611 | 200 | 605 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 200 | 608 | 200 | 616 | 2025-11-25 |
| 2026-09-11 01:59:45 | Legacy | 200 | 644 | 200 | 654 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 357 | 401 | 333 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.