ReefAPI
Server Details
One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.
- Status
- Healthy
- Uptime
- 95.5% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Server Listing
- ReefAPI MCP
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
The tools form a clear discovery→schema→execute pipeline, and each level is explicitly differentiated (engine-level vs action-level schema). The only mild overlap is search_engines vs get_catalog, both of which surface engines, though the descriptions clearly position search as a fast pre-filter and catalog as the exhaustive fallback.
All names are snake_case and follow a verb_noun shape (get_engine_schema, get_action_schema, call_engine, search_engines, get_catalog). Minor deviation: three get_* tools versus search_* and call_*, which is readable but not a single uniform pattern.
Five tools is exactly right for a gateway server: two discovery tools, two schema-introspection tools, and one execution tool. Every tool earns its place with no redundancy.
The surface covers the full lifecycle from intent matching to validated execution, and pricing/returns are surfaced via the schema tools. Minor gaps exist, such as no dedicated credit-balance or engine-listing-by-category tool, but these are workable via get_catalog.
Available Tools
5 toolscall_engineAInspect
Call a ReefAPI engine action — POST //v1/ with params. Returns the uniform
{ ok, data, meta, error } envelope. Get param names from get_engine_schema first. Needs YOUR
ReefAPI key. The local server reads REEFAPI_KEY; the hosted server accepts an OAuth access token
(connect with OAuth and paste your key once on the consent screen — this is what ChatGPT uses),
an Authorization: Bearer <key> header, x-reefapi-key, or the key in the connection URL
(https://api.reefapi.com/mcp?key=<key>). Get a key at https://reefapi.com. Failed calls cost no
credits.
Inputs: action (required), engine (required), params.
get_action_schemaARead-onlyIdempotentInspect
FULL detail for ONE engine action: every parameter (type, required, description, allowed_values dropdown, default, example, min/max), what it returns, pricing, and a ready-to-run example_params. Call this right before call_engine so you send valid params — invalid enum values are rejected with the allowed list.
Inputs: action (required), engine (required).
get_catalogARead-onlyIdempotentInspect
The FULL ReefAPI catalog — EVERY engine with its one-line title, grouped by category. This is the whole menu (≈ a few thousand tokens); SCAN IT AND PICK THE BEST ENGINE YOURSELF. You are an LLM, so you match the user's intent semantically — across ANY language, typo, or phrasing — far better than a keyword search can. Use this whenever search_engines didn't surface the right engine (or to be sure you didn't miss a better one). After you pick: get_engine_schema(engine) -> get_action_schema -> call_engine.
Inputs: no named parameters.
get_engine_schemaARead-onlyIdempotentInspect
COMPACT overview of ONE engine: every action with its description, required params and what it returns — but NOT the full param detail (kept lean so a 90-action engine stays token-cheap). Call this after search_engines to pick the right ACTION, then get_action_schema(engine, action) for that action's full params before call_engine.
Inputs: engine (required).
search_enginesARead-onlyIdempotentInspect
Find the right ReefAPI engine for a task — pass ENGLISH keywords or a short natural-language use-case ("detect a website's tech stack", "company reviews", "check a package for vulnerabilities", "is this domain available"). The catalog is in English: if the end-user asked in another language, translate their INTENT into English keywords first (you are an LLM — do this inline). Ranks engines by how well the query matches each engine's name/title/category/ACTION descriptions (stem-matched, so plurals/word-forms still hit). Empty query = list all. Returns name/title/category/actions + match score. Call this FIRST, then get_engine_schema(engine) to pick an action. This is a fast keyword pre-filter — if the right engine isn't in the results (or you want to be sure), call get_catalog and pick from the full list YOURSELF (you semantically match any language/phrasing better than keywords).
Inputs: query.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
One MCP server for all web data. Scrape, search, crawl, and AI research in one install.
380+ live data, validation and utility APIs in one MCP server: IP, DNS, email, FX, weather and more.
Web scraping MCP server — scrape, extract structured data, screenshot any site with anti-bot bypass.
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
Related MCP Servers
AlicenseCqualityBmaintenanceHosted MCP server for 3926 structured public web-data tools across 488 platform groups, returning clean JSON for search, maps, commerce, social, and finance.14500143 npm1MIT- AlicenseAqualityCmaintenanceRemote MCP server with 19 e-commerce and IP-compliance data tools — Amazon product/review/search/niche/bestseller data, AI SERP & keyword trends, local Maps POI, WIPO trademark search, and PACER patent litigation. No scraping code or proxies needed; one API key unlocks all tools.211MIT
- AlicenseAqualityCmaintenanceMCP server for agent-friendly web scraping with adaptive anti-bot bypass, dynamic rendering, and structured data extraction via 12 tools.12MIT

novada-mcpofficial
AlicenseAqualityBmaintenanceOne MCP server. All web data. Search, scrape, crawl, proxy, and AI research — in a single npx command.343MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.