# io.github.reefapi/reefapi-mcp (remote · api.reefapi.com)

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

- Trust score: 67/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.reefapi.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/reefapi-reefapi-mcp/api.md), [page](https://verifymcp.io/servers/reefapi-reefapi-mcp/api)

## Channel facts

- Endpoint: `https://api.reefapi.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1264 tokens (~252/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http reefapi-reefapi-mcp https://api.reefapi.com/mcp
```

### Codex

```toml
[mcp_servers.reefapi-reefapi-mcp]
url = "https://api.reefapi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reefapi-reefapi-mcp": {
      "type": "remote",
      "url": "https://api.reefapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add reefapi-reefapi-mcp --url https://api.reefapi.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  reefapi-reefapi-mcp:
    url: "https://api.reefapi.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "reefapi-reefapi-mcp": {
      "type": "http",
      "url": "https://api.reefapi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (5)

### `search_engines` (~265 tokens)

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

Input parameters:

- `query` (string): English keywords or a short use-case, e.g. 'company reviews', 'detect a website's tech stack', or 'is this domain available'. Translate non-English intent to English first. Empty = list all engines.

### `get_engine_schema` (~139 tokens)

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.

Input parameters:

- `engine` (string, required): The engine's name (the `engine`/`name` field from search_engines or get_catalog, e.g. 'zillow', 'amazon'). Returns each action with its description, required params, and what it returns.

### `get_action_schema` (~163 tokens)

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.

Input parameters:

- `action` (string, required): The action's name on that engine (from get_engine_schema, e.g. 'search'). Returns the full param detail (type, required, allowed_values, default, example, min/max), what it returns, pricing, and read…
- `engine` (string, required): The engine's name (e.g. 'zillow'), as returned by search_engines or get_catalog.

### `call_engine` (~216 tokens)

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.

Input parameters:

- `action` (string, required): The action to run on that engine (e.g. 'search'), as listed by get_engine_schema.
- `engine` (string, required): The engine's name to call (e.g. 'zillow'), as returned by search_engines or get_catalog.
- `params`: The action's parameters as a JSON object, e.g. {'query': 'NYC'}. Get the valid param names and values from get_action_schema first. Omit or pass null for actions that take none.

### `get_catalog` (~130 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/reefapi-reefapi-mcp/api#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://api.reefapi.com/mcp
- Authorisation metadata: https://api.reefapi.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/reefapi/reefapi-mcp
- Website: https://reefapi.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/reefapi-reefapi-mcp/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/reefapi-reefapi-mcp/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/reefapi-reefapi-mcp/api