WarpSearch
Server Details
Single-digit millisecond search across vectors and text. At any scale, for fraction of the cost. https://warpsearch.io/
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools serve distinct halves of a single workflow: register initiates account creation and claim_registration retrieves the API key or status after user approval. There is no overlap in action or resource, and the descriptions reinforce the sequence.
Both names use snake_case with no style mixing, but the verb patterns differ: claim_registration is verb_noun while register is a bare verb. The deviation is minor and still readable.
Only two tools are provided for a narrow registration-and-claim flow. They are well-scoped, but the surface feels thin and offers no additional operations such as cancellation or status-only polling.
The lifecycle from registration initiation through approval and API key claim is covered, including pending, approved, denied, expired, and already-claimed states. Minor gaps exist around cancellation or re-sending, but core workflows are complete.
Available Tools
2 toolsclaim_registrationClaim registrationAInspect
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).
Inputs: claim_token (required).
registerRegister for WarpSearchAInspect
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.
Inputs: email (required), name, role, agent.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Disposable private vector search + semantic RAG for AI agents. x402 pay-per-call, no account.
Cloud or self-hosted knowledge for AI agents: hybrid search, reranking, GraphRAG, scoped MCP tools.
Multi-engine search for AI agents. Trust scoring, local corpus, MCP-native. Self-hostable, BYOK.
Search and SQL on object storage: full-text, vector and hybrid search plus SQL over your data.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceA lightning-fast, self-hosted knowledge store and memory layer for AI agents-
- FlicenseAqualityCmaintenanceEnables LLMs to search open-source AI models by semantic meaning using directional coordinates and anchors, returning scored, ranked results in under 100ms.102-
- AlicenseNot gradedqualityCmaintenanceSemantic search with 98% token reduction for AI assistants.136MIT
- AlicenseAqualityBmaintenanceScoped, low-latency persistent memory layer for AI agents, Cursor, and Claude Code over Model Context Protocol with sub-50ms hybrid search.7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.