# MCP Server

Give any MCP-compatible AI agent web search, claim verification and balance checks through a hosted remote MCP server — no local process to run. The API key travels in the URL or an auth header.

`https://searchpipe.tech/mcp/?api_key=sp-YOUR_KEY`

Transport: Streamable HTTP. Treat any URL containing your key as a credential.

## Connect

Add the remote server URL to your client. Two authentication forms are supported — prefer whichever your client supports:

- **Key in the URL:** `https://searchpipe.tech/mcp/?api_key=sp-YOUR_KEY`
- **Auth header:** connect to `https://searchpipe.tech/mcp/` with an `Authorization: Bearer sp-YOUR_KEY` header (or `X-API-Key: sp-YOUR_KEY`).

```
claude mcp add --transport http searchpipe "https://searchpipe.tech/mcp/?api_key=sp-YOUR_KEY"
```

## Tools

Three tools are exposed. Tool names and parameters match the REST API; REST-only request metadata (`request_id`, `response_time`, `usage`, `warnings`, `notices`) remains null over MCP.

### `searchpipe_search`

REST counterpart: `POST /v1/search` · 0.5 / 1 / 2 credits by search_depth

Execute a web search: multi-engine retrieval, full-text fetching, LLM reranking and an optional cited answer or structured output. Returns the same result list as the REST endpoint.

Accepts the same parameters as POST /v1/search except stream — see the Search API reference for every parameter and default. See the [Search API reference](https://searchpipe.tech/docs/search).

### `searchpipe_verify`

REST counterpart: `POST /v1/verify` · 1 credit per claim; failed calls are refunded

Verify a factual claim against live web evidence: four-label verdict (supported / partial / unsupported / inconclusive) with span-level quotes, machine-readable reason codes and source authority. Typically takes 5-15 seconds.

**searchpipe_verify parameters**

| Parameter | Type | Description |
| --- | --- | --- |
| `claim` | string · required | The claim (statement or citation) to verify; up to 2,000 characters. |
| `mode` | string · default auto | Evidence route: paper (DOI/arXiv), web, or auto — a DOI or arXiv signal picks the paper route. |
| `evidence_urls` | string[] · optional | Up to 5 caller-supplied citation URLs to check. |
| `max_evidence` | integer · default 5 | Maximum number of evidence items to return (1-10). |

### `searchpipe_account_balance`

REST counterpart: `GET /v1/account/balance` · Free to call — no credits charged, no usage logged

Check the remaining credit balance for the key: total balance, permanent credits, expiring subscription credits, upcoming credits and the next expiry date.

## REST API vs MCP Server

Both paths run the same pipeline with the same credit balance — pick per consumer, not per project.

| Aspect | REST API | MCP Server |
| --- | --- | --- |
| Best for | Your application or backend | An MCP-compatible agent or client |
| Transport | HTTPS + JSON; optional SSE | Streamable HTTP (MCP) |
| Parameters | Full search request, including stream | Search parameters except stream |
| Response | Search content and request metadata | Same search content; REST-only request_id, response_time, usage, warnings, and notices remain null |
| Billing | 0.5 / 1 / 2 credits by depth | Same search costs and shared credit balance |
| Caching | Shared search cache; cache hits are charged | Same cache and billing behavior |

## Client configuration

Step-by-step config snippets for Claude Code, Cursor, OpenAI Codex, OpenCode, Pi and custom MCP agents live in the [agent setup guide](https://searchpipe.tech/agents); connection troubleshooting and key management live in the [MCP setup guide](https://searchpipe.tech/mcp-server). Programmatic integration paths (Python and TypeScript SDKs, directories) are cataloged in [Integrations](https://searchpipe.tech/integrations).

## Related pages

[Search API product page](https://searchpipe.tech/search-api)[Search API reference](https://searchpipe.tech/docs/search)[Verify API reference](https://searchpipe.tech/docs/verify)[FAQ](https://searchpipe.tech/faq)