Skip to content

WarpSearch MCP server

io.github.warpsearchio/warpsearchwarpsearchiostreamable-httpv07c29b2c5d6b306682ac528fc1111fc301ce64f4Scanned

Serverless hybrid search: full-text, vector and faceted search, in SQL, ES DSL, Solr and more.

2 tools: 2 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 WarpSearch MCP server can do

The WarpSearch MCP server is published by the GitHub account warpsearchio. It has 2 tools. It can create or change data (2 tools: claim_registration and register), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (register).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 07c29b2c5d6b306682ac528fc1111fc301ce64f4.

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.

2 tools

Changes things 2Claude Code: ask
  • claim_registrationCheck on a registration, and receive the API key once your user has approved it.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.
    Description, as the server wrote it
    Check on a registration, and receive the API key once your user has approved it. Returns status: pending (not approved yet; ask your user to finish, then call again), approved (with api_key, shown only this once, and how to reconnect with it), denied, expired, or claimed (the key was already handed out).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
  • registerAsk WarpSearch for an account and an API key for your user.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.

    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
    Ask WarpSearch for an account and an API key for your user. Use only an email address your user gave you for this, with their consent. The address must be a work address at your user's organization's own domain. Personal and free mailbox providers (gmail.com, outlook.com, hotmail.com, yahoo.com, icloud.com, proton.me, disposable addresses and the like) are refused with code personal_email during the public preview; ask your user for their work address instead of retrying. WarpSearch emails that address. Your user follows the link, creates the account if they have none, checks that the code matches the user_code you show them, and approves, choosing the organization and the role you get. Nothing is created until they approve, and the answer is the same whether or not the address already has an account. Returns user_code (show it to your user), claim_token (keep it secret; pass it to claim_registration), expires_at and next_steps. Each address gets at most 3 sign-up emails an hour.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false

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 write1
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, 18:24 UTC, unchanged since Oct 29, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.warpsearch.io/mcp: tools/list returned 2 tools to an anonymous client, including claim_registration (write), register (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 07c29b2c5d6b306682ac528fc1111fc301ce64f4. Values in angle brackets are yours to fill in.

claude mcp add --transport http warpsearch https://api.warpsearch.io/mcp
claude mcp add --transport http warpsearch https://api.warpsearch.io/mcp

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__warpsearch__claim_registration",
      "mcp__warpsearch__register"
    ],
    "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 warpsearch. Review it before you use it.

Capability tags behind 1 rule
  • mcp__warpsearch__register 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/io.github.warpsearchio/warpsearch/verify?hash=e62b8ee811ab136a526e7e257af4ec2acd60f3818f8b66b8a293138360d0d97a" | jq -e '.changed == false'

Pinned hash e62b8ee811ab, from Nov 10, 2026, 04:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.warpsearchio/warpsearch/changes.xml

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

Badge

Anlyon Radar badge for io.github.warpsearchio/warpsearch
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.warpsearchio/warpsearch.svg)](https://radar.anlyon.com/servers/io.github.warpsearchio/warpsearch)

Source: MCP Registry. Synced Oct 28, 2026, 21:17 UTC.

WarpSearch MCP server: questions and answers

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

Is the WarpSearch MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 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 WarpSearch MCP server delete data?

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

Can the WarpSearch 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 WarpSearch MCP server have?

2 tools: 2 write. claim_registration and register.

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

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

Does the WarpSearch MCP server send data to outside services?

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

Has the WarpSearch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.