# reefapi-mcp MCP server

One MCP for 160+ live web-data APIs — clean JSON from sites that block scrapers.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-reefapi-reefapi-mcp
- Repository: https://github.com/reefapi/reefapi-mcp
- Website: https://reefapi.com/mcp

## Install
- Endpoint: https://api.reefapi.com/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://api.reefapi.com/mcp
- Header: Authorization

## Tools
- search_engines - 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). Endpoint: https://api.reefapi.com/mcp
- get_engine_schema - 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. Endpoint: https://api.reefapi.com/mcp
- get_action_schema - 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. Endpoint: https://api.reefapi.com/mcp
- call_engine - Call a ReefAPI engine action — POST /<engine>/v1/<action> 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. Endpoint: https://api.reefapi.com/mcp
- get_catalog - 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. Endpoint: https://api.reefapi.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.reefapi
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jun 23, 2026
- Source: https://registry.modelcontextprotocol.io