An agent can connect on its own if it already holds SEARCHPIPE_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: searchpipe_search (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); searchpipe_verify (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
pass
tools.token_costabout 795 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
pass
stability.changes5 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package
2 tools, about 795 tokens to load them all · tool set b03f79362887 · tools last changed 2026-10-18 · checked 2026-10-19 10:20 UTC
Tool changes
searchpipe_searchchangedoutput schema
searchpipe_searchchangedoutput schema
searchpipe_verifyadded
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").
searchpipe_searchchangedoutput schema
searchpipe_searchchangeddescription
before
Run an AI-powered web search for a query: SearXNG retrieval → page fetching → LLM reranking → optional AI answer.
Uses the same commercial pipeline 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.
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[]).
Returns a tool error on authentication failure, insufficient credits, content violation, or retrieval failure.
after · 96% of words in common
Run an AI-powered web search for a query: multi-engine retrieval → page fetching → LLM reranking → optional AI answer.
Uses the same commercial pipeline 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.
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[]).
Returns a tool error on authentication failure, insufficient credits, content violation, or retrieval failure.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://searchpipe.tech/mcp/streamable-http
api_key ${SEARCHPIPE_TOKEN}
yes
93%
895 ms
2025-11-25
2026-10-19
Tools (2)
searchpipe_search
Run an AI-powered web search for a query: multi-engine retrieval → page fetching → LLM reranking → optional AI answer.
Uses the same commercial pipeline 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.
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[]).
Returns a tool error on authentication failure, insufficient credits, content violation, or retrieval failure.
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").