ReefAPI
REMOTE · API.REEFAPI.COM · SCANNED SEP 20
One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ReefAPI MCP server?
ReefAPI is a hosted endpoint at https://api.reefapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.reefapi.com
claude mcp add --transport http reefapi-reefapi-mcp 'https://api.reefapi.com/mcp'
{
"mcpServers": {
"reefapi-reefapi-mcp": {
"url": "https://api.reefapi.com/mcp"
}
}
} {
"servers": {
"reefapi-reefapi-mcp": {
"type": "http",
"url": "https://api.reefapi.com/mcp"
}
}
} [mcp_servers.reefapi-reefapi-mcp] url = "https://api.reefapi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"reefapi-reefapi-mcp": {
"type": "remote",
"url": "https://api.reefapi.com/mcp",
"enabled": true
}
}
} openclaw mcp add reefapi-reefapi-mcp --url 'https://api.reefapi.com/mcp' --transport streamable-http
mcp_servers:
reefapi-reefapi-mcp:
url: "https://api.reefapi.com/mcp" {
"McpServers": {
"reefapi-reefapi-mcp": {
"Transport": "http",
"Url": "https://api.reefapi.com/mcp"
}
}
} assistant mcp add reefapi-reefapi-mcp -t streamable-http -u 'https://api.reefapi.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 5 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.reefapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reefapi.com | CN=WE1,O=Google Trust Services,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d40bcc84cebada6a133507d438025cb4 |
| SANs: reefapi.com, *.reefapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.reefapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| reefapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.reefapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.reefapi.com/mcp | HTTPS enforced | 301 | https://api.reefapi.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_engine ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The action to run on that engine (e.g. 'search'), as listed by get_engine_schema. |
| engine | string | yes | 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. |
No output schema declared.
No examples provided.
get_action_schema ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 | yes | The engine's name (e.g. 'zillow'), as returned by search_engines or get_catalog. |
No output schema declared.
No examples provided.
get_catalog ~130
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_engine_schema ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | 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. |
No output schema declared.
No examples provided.
search_engines ~265
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
What is the ReefAPI MCP server?
ReefAPI is an MCP server listed in the public MCP registry as io.github.reefapi/reefapi-mcp. One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers. This page covers its hosted endpoint (https://api.reefapi.com/mcp).
Is the ReefAPI MCP server safe to use?
ReefAPI scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ReefAPI MCP server expose?
ReefAPI exposes 5 tools: search_engines, get_engine_schema, get_action_schema, call_engine, get_catalog. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.
Does the ReefAPI MCP server require authentication?
No. We connected to ReefAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ReefAPI MCP server still maintained?
ReefAPI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.