Skip to content

SearchPipe MCP server

tech.searchpipe/searchpipesearchpipe.techstreamable-httpv2.0.1Scanned

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

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SearchPipe MCP server can do

The SearchPipe MCP server is published by searchpipe.tech, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: searchpipe_search, searchpipe_verify and searchpipe_account_balance), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (searchpipe_search and searchpipe_verify).

The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 2.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • searchpipe_account_balanceCheck the remaining credit balance for this API key — free to call, no credits charged and no usage logged.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Check Credit Balance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • searchpipe_verifyVerify a factual claim against retrieved evidence: claim in, verdict out — a four-label judgment (supported / partial / unsupported / inconclusive), not generated text.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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").

    Annotations the server declares

    • title: Claim Verification
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://searchpipe.tech/mcp/: tools/list returned 3 tools to an anonymous client, including searchpipe_search (write), searchpipe_verify (write), searchpipe_account_balance (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "searchpipe_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "searchpipe_search" says "search": a word for reading.

    What this check looks for
  • The description is 2,113 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...cient credits, content violation, invalid parameters (422), or retrieval failure."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
  2. Tools1 added.+1 addedView diff

Install

Pinned to version 2.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http searchpipe https://searchpipe.tech/mcp/ --header 'Authorization: <your-authorization>'
claude mcp add --transport http searchpipe https://searchpipe.tech/mcp/ --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__searchpipe__searchpipe_search",
      "mcp__searchpipe__searchpipe_verify",
      "mcp__searchpipe__searchpipe_account_balance"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as searchpipe. Review it before you use it.

Capability tags behind 2 rules
  • mcp__searchpipe__searchpipe_search untrusted-input
  • mcp__searchpipe__searchpipe_verify untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/tech.searchpipe/searchpipe/verify?hash=df57fb0a4d68043fd4e0c96f45597c50d15af349e6a1040e0f2265b0cd5dbb3f" | jq -e '.changed == false'

Pinned hash df57fb0a4d68, from Nov 20, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/tech.searchpipe/searchpipe/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for tech.searchpipe/searchpipe
[![Anlyon Radar](https://radar.anlyon.com/badge/tech.searchpipe/searchpipe.svg)](https://radar.anlyon.com/servers/tech.searchpipe/searchpipe)

Source: MCP Registry · repository. Synced Nov 6, 2026, 03:17 UTC.

SearchPipe MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SearchPipe MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SearchPipe MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SearchPipe MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SearchPipe MCP server have?

3 tools: 3 write. searchpipe_search, searchpipe_verify and searchpipe_account_balance.

Does the SearchPipe MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SearchPipe MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SearchPipe MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.