WarpSearch
REMOTE · API.WARPSEARCH.IO
Serverless hybrid search: full-text, vector and faceted search, in SQL, ES DSL, Solr and more.
Available components
Last scanned (17 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.warpsearch.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.warpsearch.io | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 18 Oct 2026 | 3 May 2027 | RSA 2048 | SHA256-RSA | 2cd6d29ca6c622061f79f50457b6fd3 |
| SANs: api.warpsearch.io | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.warpsearch.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| warpsearch.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.warpsearch.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.warpsearch.io/mcp | HTTPS enforced | 301 | https://api.warpsearch.io:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claim_registration Claim registration ~89
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).
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | yes | the claim_token register returned |
No output schema declared.
No examples provided.
register Register for WarpSearch ~353
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | who you are, e.g. 'Claude Code on Ada's laptop'; shown to your user when they approve |
| string | yes | 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… |
No output schema declared.
No examples provided.
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.
remote · api.warpsearch.io
claude mcp add --transport http warpsearchio-warpsearch 'https://api.warpsearch.io/mcp'
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.