SearchPipe
REMOTE · SEARCHPIPE.TECH · SCANNED SEP 20
Real-time web search for AI agents: ranked results, source URLs, and optional AI answers.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 186 tokens (~186/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 6 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
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
claude mcp add --transport http tech-searchpipe-searchpipe 'https://searchpipe.tech/mcp/'
{
"mcpServers": {
"tech-searchpipe-searchpipe": {
"url": "https://searchpipe.tech/mcp/"
}
}
} {
"servers": {
"tech-searchpipe-searchpipe": {
"type": "http",
"url": "https://searchpipe.tech/mcp/"
}
}
} [mcp_servers.tech-searchpipe-searchpipe] url = "https://searchpipe.tech/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-searchpipe-searchpipe": {
"type": "remote",
"url": "https://searchpipe.tech/mcp/",
"enabled": true
}
}
} openclaw mcp add tech-searchpipe-searchpipe --url 'https://searchpipe.tech/mcp/' --transport streamable-http
mcp_servers:
tech-searchpipe-searchpipe:
url: "https://searchpipe.tech/mcp/" {
"McpServers": {
"tech-searchpipe-searchpipe": {
"Transport": "http",
"Url": "https://searchpipe.tech/mcp/"
}
}
} assistant mcp add tech-searchpipe-searchpipe -t streamable-http -u 'https://searchpipe.tech/mcp/'
{
"mcpServers": {
"tech-searchpipe-searchpipe": {
"type": "http",
"url": "https://searchpipe.tech/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 15 Sept 26 +8
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 3.4.7 ▼ security
- Tool “ai_search_search” was removed ▼ security
- Judged manipulation: unverified → pass ▲ security
- The server changed its declared name: ai-search → searchpipe security
- Schema quality: unverified → good ▲ functional
- New tool “searchpipe_search” functional
- 14 Sept 26 55
First indexed and scored.
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 20 Sept 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 Aug 2026 | 21 Nov 2026 | RSA 2048 | SHA256-RSA | 5c260745f17d489b1cec2deb6157e60f809 |
| 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/ |
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 →
searchpipe_search ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| include_answer | boolean | – | – |
| include_raw_content | boolean | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_generated | boolean | – | Whether the response contains LLM-generated content |
| answer | – | – | LLM-generated answer (optional) |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
What is the SearchPipe MCP server?
SearchPipe is an MCP server listed in the public MCP registry as tech.searchpipe/searchpipe. Real-time web search for AI agents: ranked results, source URLs, and optional AI answers. This page covers its hosted endpoint (https://searchpipe.tech/mcp/).
Is the SearchPipe MCP server safe to use?
SearchPipe scores 63 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 1 tool: searchpipe_search. Their descriptions and schemas cost roughly 186 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.