SearchPipe

Name: SearchPipe
Author: SearchPipe

Server Details

Real-time web search for AI agents: ranked results, source URLs, and optional AI answers.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 94.4% over 22 days
Last Tested: 2026-10-05 07:13
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: SearchPipe/searchpipe-mcp
GitHub Stars: 0

TDQS

A3.9/5.0

Scored 2026-09-29 04:00 across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of selecting the wrong one; its purpose (run an AI-powered web search) is unambiguous. No overlap or boundary confusion exists in this set.

Naming Consistency4/5

The single name `searchpipe_search` is clear snake_case with the server prefix plus the action, which is a predictable verb_noun-style convention. However, a one-tool set provides no evidence of a sustained pattern, so it cannot be a perfect 5.

Tool Count3/5

The server exposes one wrapper around a single commercial search pipeline, so the count is defensible for the narrow purpose. Still, one tool is thin for anything an agent might want to manage on this service (e.g. credits or usage), making it borderline under-scoped.

Completeness3/5

The core domain operation (search with answer/reranking) is covered, and errors are surfaced via tool errors. But the description references authentication, credit charging, and usage logging with no tool to check credit balance, usage, or key validity, leaving agents without recovery paths when a call fails.

Available Tools

1 tool

searchpipe_searchAInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes
`api_key`	No
`max_results`	No
`include_answer`	No
`include_raw_content`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`query`	Yes
`answer`	No	LLM-generated answer (optional)
`results`	Yes
`ai_generated`	No	Whether the response contains LLM-generated content

TDQS

A3.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses the commercial pipeline, authentication, rate limiting, moderation, credit charging, refund on failure, usage logging, and specific tool error conditions. This is rich operational transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then layers in necessary behavioral details. It is somewhat long but remains information-dense, with only minor repetition between the initial pipeline summary and the commercial pipeline breakdown.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no annotations and low schema description coverage, so the description must compensate. It does an excellent job on behavior, errors, and authentication, but it leaves several input parameters unexplained, making it only partially complete for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only documents api_key semantics (prefix, environment variable, precedence). It does not explain max_results, include_answer, or include_raw_content, leaving most parameters without semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Run an AI-powered web search for a query.' It clearly describes the tool's function and even outlines the internal pipeline, leaving no ambiguity about what it does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and the mention of an AI-powered web search, but the description does not explicitly state when to choose this tool over alternatives or when not to use it. It provides pipeline context rather than decision guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateSep 15, 2026
- Changedsearchpipe_search11 fields changed
  - addedOutput schema / properties / ai_generated / title
```
Added value: +"Ai Generated"
```
  - addedOutput schema / properties / answer / title
```
Added value: +"Answer"
```
  - addedOutput schema / properties / query / title
```
Added value: +"Query"
```
  - addedOutput schema / properties / results / items / properties / content / title
```
Added value: +"Content"
```
  - addedOutput schema / properties / results / items / properties / raw_content / title
```
Added value: +"Raw Content"
```
  - addedOutput schema / properties / results / items / properties / score / title
```
Added value: +"Score"
```
  - addedOutput schema / properties / results / items / properties / title / title
```
Added value: +"Title"
```
  - addedOutput schema / properties / results / items / properties / url / title
```
Added value: +"Url"
```
  - addedOutput schema / properties / results / items / title
```
Added value: +"SearchResult"
```
  - addedOutput schema / properties / results / title
```
Added value: +"Results"
```
  - addedOutput schema / title
```
Added value: +"SearchResponse"
```
2 tool updatesSep 14, 2026
- Removedai_search_search
- Addedsearchpipe_search
1 tool updateSep 14, 2026
- First observedai_search_search

Related MCP Connectors

Parallel Search MCP AOAuth
ai.parallel
The best web search for your AI Agent
Search Agent Orchestration Browser Automation
2216
Ninelayer
in.ninelayer
Agent-native search engine with live web research optimized for AI agents.
Search Agent Orchestration
2
agentsearch-mcp A
io.github.IsaiahDupree
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Search RAG Systems Browser Automation
31
search A
com.neurobird
Web search for AI agents. Ranked results with page passages already extracted, plus URL to markdown.
Search Browser Automation RAG Systems
21

Related MCP Servers

Neurobird Search MCP server
Browser Automation Search Web Scraping
seblosiv
A
license
Not graded
quality
A
maintenance
Enables AI agents to perform live web searches with ranked results and extracted page passages, plus clean markdown extraction of any URL.
Updated a month ago (2026-08-30 22:57 UTC)
MIT
AnySearchofficial
Search RAG Systems
anysearch-ai
A
license
Not graded
quality
B
maintenance
Unified real-time search engine skill for AI agents.
Updated 18 days ago (2026-09-17 10:11 UTC)
1,858
Apache 2.0
Tavily MCP
Search RAG Systems Browser Automation
pipeworx-io
A
license
Not graded
quality
B
maintenance
Enables AI agents to perform LLM-optimized web searches, retrieve recent news articles with full text, and extract clean readable content from URLs. It returns synthesized answers, ranked cited sources, and page text suitable for grounding RAG workflows.
Updated 8 days ago (2026-09-26 21:50 UTC)
106 npm
MIT
CrewAI Web Search MCP
Search Web Scraping Browser Automation
KennyWayn3
A
license
Not graded
quality
D
maintenance
Provides web search and content extraction for AI agents.
Updated 3 months ago (2026-07-11 07:32 UTC)
MIT