API Tools

warpsearch.io

Manages WarpSearch account registration and API key issuance for users.

1 endpoint2 known toolsFirst detected October 29, 2026Last detected October 29, 2026

ENDPOINT 1

https://api.warpsearch.io/mcp

No auth detected

MCP server metadata

Name: warpsearch-gateway
Version: 07c29b2c5d6b306682ac528fc1111fc301ce64f4

Capabilities

loggingtools.listChanged

Server instructions

WarpSearch is a serverless hybrid search service: full-text (BM25), vector and faceted search over JSON documents, plus analytics (facets, metrics, date histograms), graph neighborhood retrieval and shortest paths. It understands SQL (MySQL and PostgreSQL dialects, with tsquery full text and pgvector distances), Elasticsearch/OpenSearch Query DSL, Apache Solr, Lucene, Grafana, LogQL and its native WarpSearch language, so query it in the language you know best. Data lives in collections: index JSON documents into one, then search it. Use it as a search backend for an app, for log and event analytics, or as memory you can search. You are connected without credentials, so only account registration is available here. - If your user already has a WarpSearch API key (ws_live_...), reconnect to this server with the header "Authorization: Bearer <key>". - Otherwise, call register with your user's email address. Use only an address your user gave you for this, with their consent; never guess one. WarpSearch emails them; in their browser they create the account if they have none, check the code you show them, and approve your access. Then call claim_registration for an API key and reconnect with it.

Known tools 2

claim_registration

Check on a registration, and receive the API key once your user has approved it.

Inferred read-only

register

Ask WarpSearch for an account and an API key for your user.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.warpsearch-gateway]
url = "https://api.warpsearch.io/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: warpsearch-gateway
Remote MCP URL: https://api.warpsearch.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "warpsearch-gateway": {
      "url": "https://api.warpsearch.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "warpsearch-gateway",
  "transport": "streamable-http",
  "url": "https://api.warpsearch.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for warpsearch.io was fetched 2026-10-30T23:52:26.652Z.

Trust status Neutral

warpsearch.io is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.