One MCP server that gives assistants access to 250+ live web-data APIs through five generic tools, with automatic engine discovery and clean JSON results from hard-to-scrape public pages.
Search engines by English keywords or natural-language use-cases to find the best match (keyless).
Browse the full catalog of every engine grouped by category (keyless).
Inspect compact engine schemas and full action schemas with params, defaults, examples, and pricing (keyless).
Call any engine action with a ReefAPI key; all responses use a uniform { ok, data, meta, error } envelope.
Failed or blocked calls cost no credits.
Covers e-commerce, marketplaces, social media, real estate, jobs, travel, news, finance, reviews, and company/domain intelligence.
Enables tasks like Reddit keyword search, Zillow listings, domain availability checks, Amazon price comparison, Hacker News top stories, tech-stack detection, and remote job search.
Enables product search and retrieval from AliExpress, including listings, prices, and reviews.
Allows product search, price comparison, and retrieval of Amazon listings and reviews.
Provides access to Bluesky social media content, including posts and user data.
Enables search and retrieval of eBay product listings, prices, and seller information.
Allows searching and retrieving Etsy product listings, prices, and reviews.
Provides company reviews, ratings, and salary information from Glassdoor.
Enables searching and retrieving Reddit posts, comments, and community data.
Allows retrieving company and domain intelligence, such as tech stack information for Stripe.
Provides access to Threads social media content, including posts and user profiles.
Enables searching and retrieving TikTok videos, trends, and user data.
Allows retrieval of business reviews and ratings from Trustpilot.
Provides real estate data including property listings, prices, and details from Zillow.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ReefAPI MCP Compare Amazon prices for AirPods Pro."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
One MCP server for 250+ live web-data APIs — e-commerce and marketplaces, social media, real estate, jobs, travel, news, finance, and company/domain intelligence. The assistant discovers the right engine, then pulls clean JSON from public pages that are hard to scrape (JavaScript rendering, anti-bot).
🌐 Homepage: https://reefapi.com
📚 Docs: https://reefapi.com/docs
🔌 MCP guide: https://reefapi.com/mcp
🟢 Status: https://reefapi.com/status
Emitting one tool per API blows past the ~30–50-tool ceiling where agents stop picking the right tool. ReefAPI uses dynamic discovery instead: five generic tools let the assistant find the right engine, then call it. Discovery is keyless; only call_engine needs a key. Failed or blocked calls cost nothing.
Related MCP server: Frostbyte MCP
Tool | Keyless | What it does |
| ✅ | Ranks the catalog against English keywords or a short use-case ("company reviews", "is this domain free") and returns the best-matching engines with their actions. |
| ✅ | Returns the full menu — every engine with a one-line title, grouped by category — so the model can pick semantically when a keyword search misses. |
| ✅ | Compact overview of one engine: each action with its description, required params, and return shape, kept lean so a large engine stays token-cheap. |
| ✅ | Full detail for a single action: every parameter with type, allowed values, default, example, plus pricing and ready-to-run example params. |
| 🔑 | Runs the action and returns the uniform |
The intended path is search_engines (or get_catalog) → get_engine_schema → get_action_schema → call_engine.
Add to Claude Desktop, Cursor, Windsurf, or any client that takes a remote MCP URL:
{
"mcpServers": {
"reefapi": {
"url": "https://api.reefapi.com/mcp",
"headers": { "Authorization": "Bearer YOUR_REEFAPI_KEY" }
}
}
}Claude Code (CLI):
claude mcp add --transport http reefapi https://api.reefapi.com/mcp \
--header "Authorization: Bearer YOUR_REEFAPI_KEY"Get a free key (1,000 credits, no card) at https://reefapi.com.
pip install -r requirements.txt
export REEFAPI_KEY=ak_live_your_key # Windows: set REEFAPI_KEY=...
python server.py # stdio transportThen point your client at python /path/to/server.py. The same file also serves the streamable-HTTP
transport with MCP_TRANSPORT=streamable-http (used by the hosted endpoint above).
Each example below is answered by one engine; the link goes to that engine's parameters and response shape.
"What are people saying about the new iPhone on Reddit?" → reddit
"Get current Zillow listings in Austin under $500k." → zillow
"Is the domain coolstartup.ai available?" → domain-availability
"Compare Amazon prices for AirPods Pro." → amazon
"Top Hacker News stories right now." → hackernews
"What tech stack does stripe.com run on?" → domain-intel
"Find remote backend jobs posted this week." → global-jobs
You never have to name the engine yourself — that is what search_engines is for. The links are there for
when you want to see the exact params and fields before wiring a call.
250+ engines across E-commerce, Social Media, Real Estate, Jobs, Travel, News, Finance,
Media/Film, Reputation/Reviews, Company/Domain intelligence, and developer utilities.
Browse the full catalog at reefapi.com/docs, or call get_catalog() for the
live list. A few of the most-used ones:
Engine | Returns |
Product search, listing detail, prices, variants and reviews | |
Listings, item detail and sold/completed pricing | |
Product search and detail, including per-SKU pricing and images | |
For-sale and rental listings, property detail and value estimates | |
Listings and market data as a second US real-estate source | |
Subreddit and keyword search, post detail and comment threads | |
Posts, profiles and search across the AT Protocol network | |
Company reviews, ratings and salary data | |
Business profiles and customer reviews with ratings | |
Job search and posting detail across country sites | |
DNS, WHOIS and detected tech stack for a domain | |
Article search and extraction across news sources |
Every engine returns the same { ok, data, meta, error } envelope and draws on one shared credit pool.
Side-by-side pages with published prices on both sides and findings from our own live calls, including the cases where the other tool is the better pick:
Bright Data · DataForSEO · SerpApi · Apify · Oxylabs · ScraperAPI · ScrapingBee · ZenRows · Zyte · Firecrawl · Diffbot · Octoparse · ParseHub
MIT — see LICENSE. The APIs are a hosted service with a free tier; see https://reefapi.com.
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 reads the Authorization: Bearer ak_live_... header you configure on the connection). Get a key at https://reefapi.com.
Failed calls cost no credits.
Inputs: action (required), engine (required), params.
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).
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.
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).
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose: search/find engines, get overview or full detail of actions, and call actions. No overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores, e.g., 'call_engine', 'get_action_schema', 'search_engines'.
Five tools cover the full workflow of discovering, inspecting, and calling ReefAPI engines without being excessive or insufficient.
The set provides a complete lifecycle: search/catalog for discovery, schema retrieval for parameter details, and execution. No obvious gaps.
Your agent needs live data — a competitor's traffic, who to contact there, what people are saying, what Google and ChatGPT answer about you, a company's filings. Normally that is six vendor accounts, six sets of keys and six SDKs. This is one URL. **What you can ask for** • "How much traffic does stripe.com get, where does it come from, and who competes for the same keywords?" • "Find 20 Series-B fintech companies in Germany and the heads of marketing there, with emails." • "Does ChatGPT mention our brand when someone asks for the best CRM — and what does it cite?" • "What is X saying about $NVDA today, and what did the stock actually do?" • "Search the web for this, then scrape the three best pages into markdown." **How to use it** Point any MCP client at https://mcp.aisa.one/mcp and sign in with OAuth — there is no key to create or paste. Then just ask: the agent calls search to find the right operation and use to run it. **Why this rather than the source** 26 sources behind one account and one bill — DataForSEO, Semrush, Ahrefs, Similarweb, Apollo, X/Twitter, Instagram, Reddit, Pinterest, YouTube, Tavily, Exa, Perplexity, Firecrawl, CoinGecko, Kalshi, Polymarket, AgentMail and more, 580+ operations. tools/list returns five tools, not 580, so the introduction does not eat your context window. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** One slice at a time: https://mcp.aisa.one/seo/mcp · /finance/mcp · /social/mcp · /search/mcp · /sales/mcp · /mail/mcp · /gtm/mcp, or a single provider like /twitter-api/mcp. Same account, fewer tools listed, and search still reaches everything. Full list at https://mcp.aisa.one/servers
Your agent needs the open web — searched by more than one engine, and read as clean markdown rather than raw HTML. **What you can ask for** • "Search this question with two providers and tell me where they disagree." • "Scrape these 40 URLs into markdown, in one batch." • "Crawl this documentation site and give me every page." • "Do deep research on this topic and cite the sources." • "Find the academic papers behind this claim." **How to use it** Point any MCP client at https://mcp.aisa.one/search/mcp and sign in with OAuth — there is no key to create or paste. 30 tools across several independent providers: Tavily and Exa search, answers, contents and agent runs; Firecrawl scrape, batch scrape, crawl, map and search; Perplexity Sonar, Sonar Pro, reasoning and deep research; Oxylabs AI search and LLM jobs; OpenAI and Anthropic web search; and scholarly search. **Why this rather than the source** Several independent indexes behind one account, because one engine's blind spot is not visible from inside it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the page here, then ask the same agent who links to it or how much traffic it gets — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for the Google results page itself, https://mcp.aisa.one/seo-serp-other-engines/mcp for Bing, Baidu and Naver.
Web search API and MCP server for developers building AI agents.
One MCP server for all web data. Scrape, search, crawl, and AI research in one install.
