ReefAPI

io.github.reefapiPublished by GitHub account reefapiv1.27.2Updated Oct 24, 2026

One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

ReefAPI exposes 180+ live web-data APIs through one remote MCP server, letting an assistant find an engine, inspect its schema and call it for clean JSON.

What you can do
Search the engine catalog by English keywords or a use-case description, or fetch the full catalog grouped by category to pick an engine yourself. Read a compact overview of one engine's actions, then full parameter detail for a single action, including pricing and example parameters. Call an engine action and receive a uniform JSON envelope with data, metadata and errors.
When to use it
Useful when an assistant needs structured web data from sites that block scrapers, such as tech-stack detection, company reviews, package vulnerability checks or domain availability, and you want one key covering many data sources instead of separate integrations.
Requirements
A remote streamable HTTP endpoint at api.reefapi.com. A ReefAPI account and API key are required, sent as a bearer token in the Authorization header; the instructions also mention a REEFAPI_KEY variable for a local server and OAuth access tokens for the hosted server. Network access is needed.
Before you install
The API key is a secret sent in the Authorization header and should be kept out of logs and shared transcripts. Engine actions may be priced per call, so repeated calls can incur costs; check pricing in the action schema before calling. Calls send your queries and parameters to ReefAPI's servers.

Installation

In SourceWeft

  1. Open ReefAPI in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.reefapi%2Freefapi-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "reefapi": {
      "type": "http",
      "url": "https://api.reefapi.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

5

search_engines

Search ReefAPI 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).

Parametersquery

get_engine_schema

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.

Parametersenginerequired

get_action_schema

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.

Parametersactionrequiredenginerequired

call_engine

Call a ReefAPI 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 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.

Parametersactionrequiredenginerequiredparams

get_catalog

ReefAPI 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.

Takes no parameters.

Version history

1
  1. v1.27.2LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.