SearchPipe

tech.searchpipePublished by searchpipe.techOfficial publisherv2.0.1Updated Nov 6, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingAI & ML

Overview

AI-generated overview

SearchPipe is a hosted web search API and remote MCP server that gives an assistant web search, claim verification and credit-balance checks.

What you can do
  • Run AI-powered web searches with multi-engine retrieval, page fetching, LLM reranking and an optional AI answer.
  • Verify a factual claim against retrieved evidence and get a four-label verdict (supported, partial, unsupported, inconclusive) with span-level quotes and source authority.
  • Check the remaining credit balance for the API key, including permanent and expiring credits.
When to use it
Useful when an assistant needs current web results, sourced answers, or a check on whether a claim is backed by evidence, without building your own search pipeline. It fits agent workflows that want a managed search backend rather than a local scraper.
Requirements
A remote Streamable HTTP endpoint at searchpipe.tech; no local install. Requires a SearchPipe account and an sp- API key sent as a Bearer token in the Authorization header (or as a URL parameter). New accounts get free credits; further use is charged per search.
Before you install
The API key is a billable credential: keep it out of shared configs and prefer the Authorization header over a URL parameter, which can leak in logs. Searches consume credits, and the search tool passes through the commercial pipeline including input moderation. Queries and claims are sent to a third-party service.

Installation

In SourceWeft

  1. Open SearchPipe in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/tech.searchpipe%2Fsearchpipe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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

Source: README.md at commit 1dddac9

Tools

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

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

Parametersapi_key

Version history

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

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts