Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SearchPipe

REMOTE · SEARCHPIPE.TECH

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

Available components

0 this week 75 Trust /100

Last scanned (18 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1241 tokens (~413/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 22 Oct 26 +1
    • Schema quality: 505 → 413 ▲ functional
    • New tool “searchpipe_account_balance” functional
  • 20 Oct 26 −1
    • Tool “searchpipe_search” rewrote its description, which is the text the model reads security
    • Schema quality: 292 → 505 ▼ functional
    • “searchpipe_search” added an optional parameter “country” cosmetic
    • “searchpipe_search” added an optional parameter “end_date” cosmetic
    • “searchpipe_search” added an optional parameter “exclude_domains” cosmetic
    • “searchpipe_search” added an optional parameter “include_domains” cosmetic
    • “searchpipe_search” added an optional parameter “include_images” cosmetic
    • “searchpipe_search” added an optional parameter “language” cosmetic
    • “searchpipe_search” added an optional parameter “objective” cosmetic
    • “searchpipe_search” added an optional parameter “output_schema” cosmetic
    • “searchpipe_search” added an optional parameter “output_type” cosmetic
    • “searchpipe_search” added an optional parameter “safe_search” cosmetic
    • “searchpipe_search” added an optional parameter “search_depth” cosmetic
    • “searchpipe_search” added an optional parameter “start_date” cosmetic
    • “searchpipe_search” added an optional parameter “time_range” cosmetic
    • “searchpipe_search” added an optional parameter “topic” cosmetic
  • 15 Oct 26 +14
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 14 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://searchpipe.tech/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=searchpipe.tech CN=YR2,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 RSA 2048 SHA256-RSA 68195d0573059455f24a50e8b5ff72549d0
SANs: searchpipe.tech, www.searchpipe.tech
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of searchpipe.tech. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
tech. present 2185 13 Verified
searchpipe.tech. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://searchpipe.tech/mcp/ Verified 200
http (plaintext) http://searchpipe.tech/mcp/ HTTPS enforced 301 https://searchpipe.tech/mcp/
MCP tools · 3 exposed · ~1,241 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
searchpipe_account_balance ~230

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

NameTypeReqDescription
api_key–––
NameTypeReqDescription
balancenumberyes–
expiringnumberyes–
free_tier_creditsintegeryes–
next_expiry–yes–
permanentnumberyes–
unlimitedboolean––
upcomingnumber––

No examples provided.

searchpipe_search ~610

Run an AI-powered web search for a query: multi-engine retrieval → page fetching → LLM reranking → optional AI answer. Uses the same commercial pipeline and accepts the same parameters as the HTTP POST /search endpoint: authentication → rate limiting → input moderation → credit charge → search → output moderation + AI-generated marker → refund on failure → usage logging. Credits are charged per call. search_depth: "basic" (default, 1 credit) / "advanced" (2 credits) / "fast" (0.5 credit — skips all LLM steps: results keep engine order with engine-provided relevance scores, no answer is generated). include_domains / exclude_domains: restrict or exclude domains ("example.com" matches the domain and any subdomain; "*.example.com" matches subdomains only; "example.com/docs" also requires the URL path to start with /docs; exclude wins over include). time_range: recency window "day" / "week" / "month" / "year"; start_date / end_date: ISO YYYY-MM-DD bounds (results without a known publish date are not filtered). topic: "general" (default) or "news" (always adds a dedicated news channel to retrieval). country: ISO 3166-1 alpha-2 region bias (e.g. "US"); language: upstream market language (e.g. "en", "zh-CN"); combined into the upstream market locale. safe_search: 0 off (default) / 1 moderate / 2 strict. include_images: also run an image search and return an images array alongside results. output_type: "search_results" (default) / "answer" (same as include_answer=true) / "structured" (grounded JSON object per output_schema — requires output_schema; on failure output is null). objective: optional one-line search intent from the calling agent; improves reranking only. stream is REST-only and not available over MCP. 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 Tavily-style structured results (query / answer / results[] / images[] / output). Returns a tool error o…

NameTypeReqDescription
api_key–––
country–––
end_date–––
exclude_domains–––
include_answerboolean––
include_domains–––
include_imagesboolean––
include_raw_contentboolean––
language–––
max_resultsinteger––
objective–––
output_schema–––
output_type–––
querystringyes–
safe_searchinteger––
search_depthstring––
start_date–––
time_range–––
topicstring––
NameTypeReqDescription
ai_generatedboolean–Whether the response contains LLM-generated content
answer––LLM-generated answer (optional)
answer_audit––Per-statement audit of the AI answer (advanced depth only)
images––Image results (present when the request set include_images=true)
notices––How this response was produced (safe to show to the model)
output––Structured JSON object conforming to output_schema (output_type='structured' only; null when conversion failed)
querystringyes–
request_id––Unique request identifier, also returned as the X-Request-Id response header
response_time––Server processing time for this request, in seconds
resultsarrayyes–
usage––Billing and cache info for this request
warnings––Parameter-level issues: a requested feature did not take effect (safe to show the developer; do not feed to the model)

No examples provided.

searchpipe_verify ~401

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

NameTypeReqDescription
api_key–––
claimstringyes–
evidence_urls–––
max_evidenceinteger––
modestring––
NameTypeReqDescription
confidencenumberyes–
evidencesarray––
prompt_version–––
reason_codestringyes–
timingobject–Per-stage wall time in seconds
verdictstringyes–

No examples provided.

Install

How do I install the SearchPipe MCP server?

SearchPipe is a hosted endpoint at https://searchpipe.tech/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · searchpipe.tech

# add to Claude Code
claude mcp add --transport http tech-searchpipe-searchpipe 'https://searchpipe.tech/mcp/'
Common questions

What is the SearchPipe MCP server?

SearchPipe is an MCP server listed in the public MCP registry as tech.searchpipe/searchpipe. Web search API and MCP server for developers building AI agents. This page covers its hosted endpoint (https://searchpipe.tech/mcp/).

Is the SearchPipe MCP server safe to use?

SearchPipe scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SearchPipe MCP server expose?

SearchPipe exposes 3 tools: searchpipe_search, searchpipe_verify, searchpipe_account_balance. Their descriptions and schemas cost roughly 1,241 tokens of context every time the server is loaded.

Does the SearchPipe MCP server require authentication?

No. We connected to SearchPipe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SearchPipe MCP server still maintained?

SearchPipe is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.