# WarpSearch (remote · api.warpsearch.io)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `api.warpsearch.io`: 72/100 (this document), [markdown](https://verifymcp.io/servers/warpsearchio-warpsearch/api.md), [page](https://verifymcp.io/servers/warpsearchio-warpsearch/api)

## Channel facts

- Endpoint: `https://api.warpsearch.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `07c29b2c5d6b306682ac528fc1111fc301ce64f4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 717 tokens (~358/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the WarpSearch MCP server?

WarpSearch is a hosted endpoint at https://api.warpsearch.io/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.

### Claude

```bash
claude mcp add --transport http warpsearchio-warpsearch 'https://api.warpsearch.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "warpsearchio-warpsearch": {
      "url": "https://api.warpsearch.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "warpsearchio-warpsearch": {
      "type": "http",
      "url": "https://api.warpsearch.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.warpsearchio-warpsearch]
url = "https://api.warpsearch.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "warpsearchio-warpsearch": {
      "type": "remote",
      "url": "https://api.warpsearch.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add warpsearchio-warpsearch --url 'https://api.warpsearch.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  warpsearchio-warpsearch:
    url: "https://api.warpsearch.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "warpsearchio-warpsearch": {
      "Transport": "http",
      "Url": "https://api.warpsearch.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add warpsearchio-warpsearch -t streamable-http -u 'https://api.warpsearch.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "warpsearchio-warpsearch": {
      "type": "http",
      "url": "https://api.warpsearch.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 69)

First indexed and scored.

## MCP tools (2)

### `claim_registration` (~89 tokens)

Claim registration

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).

Input parameters:

- `claim_token` (string, required): the claim_token register returned

### `register` (~353 tokens)

Register for WarpSearch

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.

Input parameters:

- `agent` (string): who you are, e.g. 'Claude Code on Ada's laptop'; shown to your user when they approve
- `email` (string, required): your user's work email address, exactly as they gave it to you for this; free and personal mailbox providers (gmail.com, outlook.com, ...) are refused
- `name` (string): your user's name, if you know it (used in the email)
- `role` (string): the role you ask for: admin (default; can also delete collections), editor (can also create collections and change mappings), writer (index into existing collections) or viewer (search only). Your us…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/warpsearchio-warpsearch/api#diagnostics

## Score history

- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69

## Common questions

### What is the WarpSearch MCP server?

WarpSearch is an MCP server listed in the public MCP registry as io.github.warpsearchio/warpsearch. Serverless hybrid search: full-text, vector and faceted search, in SQL, ES DSL, Solr and more. This page covers its hosted endpoint (https://api.warpsearch.io/mcp).

### Is the WarpSearch MCP server safe to use?

WarpSearch scores 72 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 WarpSearch MCP server expose?

WarpSearch exposes 2 tools: claim_registration, register. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.

### Does the WarpSearch MCP server require authentication?

No. We connected to WarpSearch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WarpSearch MCP server still maintained?

WarpSearch is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.warpsearch.io/mcp
- Website: https://warpsearch.io/docs/agents
- Changelog RSS feed: https://verifymcp.io/servers/warpsearchio-warpsearch/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/warpsearchio-warpsearch/api.json
- HTML version of this page: https://verifymcp.io/servers/warpsearchio-warpsearch/api