Agentsearch Mcp

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

LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

概览

AI 生成的概览

远程 MCP 连接器,为智能体和 RAG 提供网页搜索、免密钥即时问答以及把网址转成干净文本的抓取能力。

可以做什么
  • 通过可切换供应商的后端搜索网页,返回带位置、标题、网址、摘要和域名的规范化结果。
  • 以免密钥的即时问答查询定义、实体和快速事实。
  • 抓取任意公开网址,返回去除样板内容的纯文本或 Markdown,便于放入大模型上下文。
适用场景
适合需要实时网页结果、快速事实查询,或需要可读页面正文用于检索与摘要的场景,无需自行搭建抓取流程。它只是对计量上游 API 的轻量转发,适合轻度探索使用,不适合高并发生产流量。
运行要求
需要一个远程 streamable-HTTP 端点;MCP 调用方无需账号、OAuth 或 API 密钥,上游代理密钥由连接器在服务端持有。抓取网页需要对外网络访问。
安装前请注意
抓取的页面内容和搜索结果来自第三方并原样返回,应视为不可信输入。按 IP 有内存中的软性速率限制,运营方称这是付费 API 之上的免费体验层,大用量应走付费渠道。所有工具均为只读。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Agentsearch Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "agentsearch": {
      "type": "http",
      "url": "https://agentsearch-mcp.vercel.app/mcp"
    }
  }
}

README

agentsearch-mcp

A remote MCP (Model Context Protocol) connector for AgentSearch API — an LLM/MCP-native web toolkit for agents and RAG pipelines: web search (provider-abstracted SERP), keyless instant answers, and URL → clean text/markdown fetch ready for an LLM context window.

Live: https://agentsearch-mcp.vercel.app/mcp — 3 tools, one per AgentSearch /v1 endpoint. Since the upstream AgentSearch deployment is metered (RapidAPI/Apify) and gates /v1/* behind a RapidAPI proxy-secret guard, this connector authenticates its own outbound calls with that same secret (AGENTSEARCH_MCP_PROXY_SECRET, sent as the X-RapidAPI-Proxy-Secret header) and applies a soft per-IP rate limit (AGENTSEARCH_MCP_RATE_LIMIT, default 30 tool-calls/hour, in-memory) so the free MCP tier stays a discovery channel rather than an unmetered bypass of the paid listing — see lib/ratelimit.js.

What this is, and why it's a separate connector

AgentSearch API is a plain REST API. Any HTTP client can already call it directly. This repo exists because MCP clients (Claude, ChatGPT, and other MCP-aware agents) don't consume arbitrary REST APIs — they consume MCP tools. agentsearch-mcp is a thin adapter layer that:

  • Exposes each AgentSearch endpoint as a discoverable, typed MCP tool (name, description, zod input schema, annotations) that an LLM can reason about and call directly, instead of having to be taught the REST surface out-of-band.
  • Speaks the MCP streamable-HTTP transport at a single /mcp endpoint, so it can be registered as a connector in Claude, ChatGPT, or any other MCP client with one URL.
  • Does nothing else. It has no business logic of its own — every tool call is a pass-through fetch to AgentSearch, and the JSON response AgentSearch returns is handed back verbatim as the tool result.

Free discovery tier over a metered API

This connector is a free discovery/growth tier in front of the metered AgentSearch API. The upstream (agentsearch-api.vercel.app) is sold on RapidAPI/Apify; this MCP wrapper authenticates to it with the shared RapidAPI proxy secret and caps usage per-IP so it stays a taste-test rather than an unmetered path around the paid plans. Heavy/production volume should go through AgentSearch on RapidAPI/Apify.

Authentication: None on the MCP side (deliberate)

AgentSearch's data has no per-user dimension — it's public web data (SERP results, DuckDuckGo instant answers, cleaned page text). There is nothing to gate per-caller, so this connector intentionally ships with:

  • No OAuth, no login, no bearer tokens for the MCP caller
  • No Supabase / database
  • No demo-vs-real account split — every caller gets the same real, live data

api/mcp.js builds a fresh, stateless McpServer per request and serves it with zero MCP-caller auth checks. The only outbound auth is the upstream RapidAPI proxy secret described above, which the connector holds server-side.

Tool list

One tool per AgentSearch /v1 endpoint (from agentsearch-api/openapi.yaml; /api/health is intentionally not wrapped):

ToolAgentSearch endpointDescription
web_searchGET /v1/searchWeb SERP via a provider-abstracted backend (Brave or Serper). Returns normalized results with position/title/url/snippet/domain.
instant_answerGET /v1/answerKeyless DuckDuckGo instant answer — definitions, entities, quick facts.
fetch_urlGET /v1/fetchKeyless, SSRF-guarded URL → clean, boilerplate-free text or markdown for RAG.

All 3 tools are read-only and annotated { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true } — none of them write anything, and all of them reflect live, externally-changing web data.

How it wraps agentsearch-api

Each tool handler does a plain fetch(\${AGENTSEARCH_MCP_API_BASE_URL}${path}`, ...)` against the real AgentSearch REST API and returns the parsed JSON as MCP tool-result content:

js
{ content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] }

The outbound request carries X-RapidAPI-Proxy-Secret: <AGENTSEARCH_MCP_PROXY_SECRET> so it passes the upstream guard on /v1/*. Upstream HTTP errors (4xx/5xx) are caught and surfaced as a typed MCP error result via an asError helper rather than crashing the request.

Environment variables

VarDefaultPurpose
AGENTSEARCH_MCP_API_BASE_URLhttps://agentsearch-api.vercel.appUpstream AgentSearch base URL (override for local/self-hosted testing).
AGENTSEARCH_MCP_PROXY_SECRET(empty)RapidAPI proxy secret, sent as X-RapidAPI-Proxy-Secret to pass the upstream /v1/* guard. Without it, guarded routes return 403.
AGENTSEARCH_MCP_RATE_LIMIT30Soft per-IP tools/call cap per hour (in-memory, per serverless instance).

Project layout

api/mcp.js       MCP endpoint (StreamableHTTPServerTransport, stateless, no MCP-caller auth)api/health.js    GET /api/healthlib/tools.js     All 3 tool definitions (zod schemas + fetch-and-forward handlers, proxy-secret auth)lib/ratelimit.js Soft per-IP tools/call rate limiterlocal-server.js  Plain-Node http server for local dev / smoke testing (not deployed)test/smoke.mjs   Real end-to-end smoke test (initialize, tools/list, tools/call)vercel.json      Routes /mcp -> api/mcp.js, /health -> api/health.jsserver.json      MCP registry manifest

Local development

bash
npm installnpm run dev          # starts local-server.js on :3900npm run smoke        # runs test/smoke.mjs against the local server

To exercise a real end-to-end fetch through the upstream guard, set the proxy secret first:

bash
export AGENTSEARCH_MCP_PROXY_SECRET=<the RapidAPI proxy secret>npm run dev &npm run smoke

来源:README.md,提交 c585fcf

工具

3

instant_answer

Instant answer (keyless)

DuckDuckGo Instant Answer API — definitions, entities, and quick facts. Returns a normalized answer with heading, type (abstract/answer/disambiguation), source, sourceUrl, optional image/definition, and relatedTopics, plus a meta envelope. Not a full web SERP; use web_search for that. Works with no API key.

输入参数q必填

fetch_url

Fetch a URL as clean text/markdown (RAG-ready)

Fetches any public http(s) URL, strips boilerplate (scripts, nav, footer, ads), and returns clean text or markdown ready for an LLM context window. SSRF-guarded — refuses private/loopback/internal hosts. Returns url, title, format, length, content (and finalUrl when redirected, plus up to 50 extracted links when links=true), with a meta envelope. Works with no API key.

输入参数url必填linksformatmaxChars

版本历史

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

评分

已满足适用检查项的 90%

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

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

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