ReefAPI

io.github.reefapi由 GitHub 账号 reefapi 发布v1.27.2更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行网页搜索与抓取数据与分析

概览

AI 生成的概览

ReefAPI 通过一个远程 MCP 服务器提供 180 多个实时网络数据 API,让助手查找引擎、查看参数结构并调用以获取干净的 JSON。

可以做什么
用英文关键词或用例描述搜索引擎目录,或获取按类别分组的完整目录自行挑选引擎。查看单个引擎的紧凑动作概览,再获取某个动作的完整参数详情,包括定价和示例参数。调用引擎动作,返回统一的 JSON 信封,包含数据、元信息和错误。
适用场景
适合助手需要从屏蔽爬虫的网站获取结构化网络数据的场景,例如技术栈识别、公司评价、软件包漏洞检查或域名可用性查询,并且希望用一个密钥覆盖多种数据源而不是分别集成。
运行要求
远程 streamable HTTP 端点 api.reefapi.com。需要 ReefAPI 账户和 API 密钥,以 bearer 令牌形式放在 Authorization 请求头中;说明中还提到本地服务器读取 REEFAPI_KEY 变量,托管服务器接受 OAuth 访问令牌。需要网络访问。
安装前请注意
API 密钥是放在 Authorization 请求头中的机密,应避免出现在日志和共享记录中。引擎动作可能按次计费,反复调用会产生费用,调用前请查看动作结构中的定价。调用会把查询和参数发送到 ReefAPI 的服务器。

安装

在 SourceWeft 中

  1. 打开 控制台中的 ReefAPI,将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.reefapi%2Freefapi-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

该仓库没有 README。

工具

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

输入参数query

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.

输入参数engine必填

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.

输入参数action必填engine必填

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.

输入参数action必填engine必填params

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.

无需输入参数。

版本历史

1
  1. v1.27.2最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。