ReefAPI MCP server
io.github.reefapi/reefapi-mcpreefapistreamable-httpv1.27.2Scanned
One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the ReefAPI MCP server can do
The ReefAPI MCP server is published by the GitHub account reefapi. It has 5 tools. It can create or change data (1 tool: call_engine), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (call_engine).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.27.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
call_engineCall a ReefAPI engine action — POST /<engine>/v1/<action> with `params`.Reads text others writeNo findings
Why it is in this group
- The name "call_engine" says "call": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Call a ReefAPI engine
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
get_action_schemaFULL 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 e…No findings
Why it is in this group
- The name "get_action_schema" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Action schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_catalogThe FULL ReefAPI catalog — EVERY engine with its one-line title, grouped by category.No findings
Why it is in this group
- The name "get_catalog" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: ReefAPI catalog
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_engine_schemaCOMPACT 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-…No findings
Why it is in this group
- The name "get_engine_schema" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Engine schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_enginesFind 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 vuln…No findings
Why it is in this group
- The name "search_engines" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Search ReefAPI engines
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The operation was aborted due to timeout
Posture changes
- Nov 20, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://api.reefapi.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://api.reefapi.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: yes to not observed
- Nov 6, 2026
- RFC 9728 protected resource metadata: none to https://api.reefapi.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.reefapi.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://api.reefapi.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://api.reefapi.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: yes to not observed
Tools5 changed.~5 changedView diff
- Changed:call_engineChanges thingsannotations
- Changed:get_action_schemaOnly readsannotations
- Changed:get_catalogOnly readsannotations
- Changed:get_engine_schemaOnly readsannotations
- Changed:search_enginesOnly readsannotations
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://api.reefapi.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://api.reefapi.com; Dynamic client registration: not observed -> yes…View diff
- RFC 9728 protected resource metadata: none to https://api.reefapi.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.reefapi.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Install
Pinned to version 1.27.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http reefapi https://api.reefapi.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http reefapi https://api.reefapi.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__reefapi__search_engines",
"mcp__reefapi__get_engine_schema",
"mcp__reefapi__get_action_schema",
"mcp__reefapi__get_catalog"
],
"ask": [
"mcp__reefapi__call_engine"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as reefapi. Review it before you use it.
Capability tags behind 1 rule
- mcp__reefapi__call_engine untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.reefapi/reefapi-mcp/verify?hash=86f9e29901aa5f58ab0377f0dbf139c14197519e9e0cfe384d258d7bf7a8ac93" | jq -e '.changed == false'Pinned hash 86f9e29901aa, from Nov 20, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.reefapi/reefapi-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.reefapi/reefapi-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.
ReefAPI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ReefAPI MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ReefAPI MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ReefAPI MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ReefAPI MCP server have?
- 5 tools: 1 write, 4 read. call_engine, search_engines, get_engine_schema, get_action_schema and get_catalog.
Does the ReefAPI MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the ReefAPI MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ReefAPI MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.