SearchPipe

tech.searchpipe由 searchpipe.tech 发布官方发布者v2.0.1更新于 Nov 6, 2026

Web search API and MCP server for developers building AI agents.

已验证Streamable HTTP可网页运行网页搜索与抓取AI 与机器学习

概览

AI 生成的概览

SearchPipe 是一个托管式网页搜索 API 与远程 MCP 服务器,让助手进行网页搜索、事实核查和查询剩余额度。

可以做什么
  • 执行 AI 驱动的网页搜索:多引擎检索、抓取页面、LLM 重排序,并可附带 AI 生成的答案。
  • 针对检索到的证据核查事实性陈述,输出四类判定(支持、部分支持、不支持、无法判定),并附片段级引文与来源权威度。
  • 查询该 API 密钥的剩余额度,包括永久额度与即将过期的额度。
适用场景
适合需要最新网页结果、有来源的答案,或判断某说法是否有证据支撑的场景,无需自行搭建搜索管线。也适合希望使用托管搜索后端而非本地抓取的智能体工作流。
运行要求
远程 Streamable HTTP 端点(searchpipe.tech),无需本地安装。需要 SearchPipe 账号,并以 Authorization 头中的 Bearer 令牌(或 URL 参数)提供 sp- 开头的 API 密钥。新账号有免费额度,之后按搜索计费。
安装前请注意
API 密钥是可计费凭证,请勿放入共享配置;优先使用 Authorization 头而非 URL 参数,后者可能出现在日志中。搜索会消耗额度,搜索工具会经过包含输入审核的商业管线。查询内容与待核查陈述会发送给第三方服务。

安装

在 SourceWeft 中

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

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "searchpipe": {
      "type": "http",
      "url": "https://searchpipe.tech/mcp/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

SearchPipe Integrations

[MCP] [SearchPipe]

Official integration packages for SearchPipe — a web search API and MCP server for developers building AI agents.

This repository contains:

  • Remote MCP endpoint — connect any MCP client to SearchPipe via Streamable HTTP (no local install needed)
  • LangChain SDK — pip install langchain-searchpipe for retriever, tool, and answer components
  • Python SDK — pip install searchpipe, official thin client over the Search API
  • TypeScript SDK — npm install searchpipe, official zero-dependency client (ESM + CJS)

The SearchPipe server itself is a managed service at searchpipe.tech. Self-hosting is available on request.

MCP Access (Remote)

Add to your MCP client config (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "searchpipe": {      "url": "https://searchpipe.tech/mcp/?api_key=sp-your-api-key-here"    }  }}

Or use an Authorization header instead of URL parameter:

json
{  "mcpServers": {    "searchpipe": {      "url": "https://searchpipe.tech/mcp/",      "headers": {        "Authorization": "Bearer sp-your-api-key-here"      }    }  }}

See claude_desktop_config.json.example for a ready-to-copy template.

LangChain Integration

bash
pip install langchain-searchpipe

See langchain-searchpipe/README.md for full usage examples (retriever, tool, answer components).

Official SDKs

Both SDKs are thin wrappers over POST /search — same parameters, same response shape as the REST API.

Python (sdks/python/):

bash
pip install searchpipe
python
from searchpipe import SearchPipe
client = SearchPipe(api_key="sp-YOUR_KEY")resp = client.search("FastAPI tutorial", max_results=5, include_answer=True)print(resp.answer)for r in resp.results:    print(r.score, r.title, r.url)

JavaScript / TypeScript (sdks/typescript/):

bash
npm install searchpipe
ts
import { SearchPipe } from "searchpipe";
const client = new SearchPipe({ apiKey: "sp-YOUR_KEY" });const resp = await client.search({ query: "FastAPI tutorial", maxResults: 5, includeAnswer: true });console.log(resp.answer);

Both default to https://searchpipe.tech and read the key from SEARCHPIPE_API_KEY. See each SDK's README for the full API, error classes, and self-hosting options.

Getting an API Key

  1. Sign up at searchpipe.tech
  2. Verify your email
  3. Go to Dashboard → API Keys → copy your sp- key
  4. New accounts receive free credits to try the service

Tool Schema

searchpipe_search

Run a web search with optional AI-generated answer.

ParameterTypeRequiredDefaultDescription
querystring✅—Search query
max_resultsinteger—5Number of results (1–20)
include_answerboolean—falseInclude AI-generated answer
include_raw_contentboolean—falseInclude full page content
api_keystring——API key (or use env var / URL param)

Returns: Tavily-style SearchResponse with query, answer, results[].

Links

License

MIT

来源:README.md,提交 1dddac9

工具

3

searchpipe_verify

Verify a factual claim against retrieved evidence: claim in, verdict out — a four-label judgment (supported / partial / unsupported / inconclusive), not generated text. Every result ships with verifiable evidence — span-level quotes, claim verdicts, and source authority — not just links. Verdict labels: `supported` = evidence text clearly supports the claim; `partial` = partly supported or weak evidence; `unsupported` = reachable evidence does not support the claim (misattributed citation detected); `inconclusive` = the claim could not be judged (fetch failure, paywall, or insufficient evidence) — the tool reports that honestly instead of guessing. Verification fetches source pages and judges claim-evidence consistency, so it typically takes 5-15 seconds. Uses the same commercial pipeline as the HTTP POST /verify endpoint: authentication → email verification → rate limiting → input moderation → per-request credit charge → verification → refund on failure → usage logging. Credits are charged per call; an inconclusive verdict is still a delivered result and is not refunded. mode: evidence route — "paper" / "web" / "auto" (default; a DOI or arXiv signal decides). evidence_urls: up to 5 caller-supplied citations to verify. max_evidence: maximum evidence items to return (1-10, default 5). api_key: an API key starting with `sp-`. It may also be provided through the SEARCHPIPE_API_KEY environment variable (the parameter takes precedence). Returns VerifyResponse (verdict / confidence / reason_code / evidences[] / timing). Returns a tool error on authentication failure, insufficient credits, content violation, verification failure, or when the verify endpoint is disabled ("Verify endpoint is not available").

输入参数modeclaim必填api_keymax_evidenceevidence_urls

searchpipe_account_balance

Check the remaining credit balance for this API key — free to call, no credits charged and no usage logged. Returns the same fields as the REST GET /v1/account/balance endpoint: `balance` (total remaining credits, 2 decimal places), `permanent` (recharge/bonus credits that never expire), `expiring` (subscription credits, valid 30 days), `upcoming` (renewal credits already granted but not active until the next cycle), `next_expiry` (soonest expiry among time-limited credits), `free_tier_credits` (free monthly allowance size) and `unlimited` (admin/owner exemption flag). Poll this before batch jobs to avoid hitting 402 insufficient-credits mid-run. Works even when the account email is not verified yet. api_key: an API key starting with `sp-`. It may also be provided through the SEARCHPIPE_API_KEY environment variable (the parameter takes precedence). Returns a tool error on authentication failure (missing, invalid, or revoked key).

输入参数api_key

版本历史

4
  1. v2.0.1最新Nov 6, 2026
  2. v2.0.0Nov 3, 2026
  3. v1.0.1Sep 30, 2026
  4. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 100%

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

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