One MCP for 160+ live web-data APIs — search, social, e-commerce, real estate, jobs, travel, news, finance. The assistant discovers the right engine, then pulls clean JSON from sites that block scrapers (captcha, login, JS, anti-bot). Discovery is keyless; calls use a free ReefAPI key.
reefapi is a remote MCP server published at mcp.reefapi.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 283 ms, placing it among the faster endpoints. It offers a narrow, focused set of 5 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.
search_engines — requires English input despite LLM's multilingual capabilitiesget_engine_schema — describes compact overview but doesn't clarify what's omittedcall_engine — param requirements mentioned but not explicitly definedget_catalog — full catalog access may overwhelm agents with too many optionsRisk: 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/support-c2w9-reefapi)<a href="https://mcpmetrics.io/servers/support-c2w9-reefapi"><img src="https://mcpmetrics.io/badge/support-c2w9/reefapi/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 15:07:20 | Legacy | 400 | 230 | 200 | 212 | 2025-11-25 |
| 2026-09-11 13:13:33 | Legacy | 400 | 283 | 200 | 286 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 246 | 200 | 225 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 295 | 200 | 294 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 235 | 200 | 216 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 358 | 401 | 357 | — |
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.