Skip to main content

MCP Server

NeuralVerge exposes its API as a remote Model Context Protocol (MCP) server, so any MCP-compatible client — Claude, ChatGPT, Cursor, or a custom agent — can call Search, AI Extract, and every Data Source (including marketplaces and product reviews) directly as tools, without writing any HTTP integration code. Every tool is a thin 1:1 wrapper around the corresponding REST endpoint documented in the API Reference tab. AI Research is not exposed over MCP — a research run is asynchronous, while an MCP tool has to return its result inside the call — so start those over the REST API.

Endpoint

The server speaks MCP’s Streamable HTTP transport and is stateless — each request is handled independently, with no session to keep alive between calls. Requests must include:

Authentication

Send the same bearer token you use for the REST API: Authorization: Bearer YOUR_ACCESS_TOKEN See Authentication for how to obtain a token. A request with a missing or invalid token is rejected with 401 Unauthorized before any tool runs.

Available tools

The server exposes 251 tools: run_search, run_extract, and one per Data Source endpoint. A client that caps how many tools it loads will see only part of the catalogue — see Tool count below.

AI Extract

Every Data Source endpoint is exposed as a tool, grouped into the same categories the Data Sources page uses in the app.

Tool count

tools/list returns all 251 tools in one response, about 150 KB of JSON. Two things follow from that:
  • A model pays for those definitions in context on every conversation that has the server attached.
  • Clients that limit the number of active tools will load only some of them, and the rest will be invisible to the model.
If you only need a few sources, attach the server to a client that lets you pick tools, or proxy it and expose the subset you use.

Data Sources — Company Registries

Data Sources — Company intelligence

Data Sources — E-commerce & Marketplaces

Data Sources — Enrichment

Data Sources — Product reviews

Data Sources — Social media

Data Sources — Startup & Funding Data

Input parameters, limits, and pricing for every Data Source tool match the REST endpoints described in Data Sources.

Synchronous results

Every tool returns its result directly in the tool response — there is no session to poll. A scrape that hits its time budget returns partial: true with the records collected so far, so a long run degrades to a shorter result instead of failing.

Connecting an MCP client

Claude Code / Claude Desktop

Generic remote HTTP client (ChatGPT, Cursor, etc.)

Add a remote MCP connector pointing at the endpoint above, with an Authorization: Bearer YOUR_ACCESS_TOKEN header. Any client that speaks MCP’s Streamable HTTP transport works — the server does not require any client-specific setup.

MCP Inspector

Connect to https://api.neuralverge.ai/functions/v1/mcp-server in HTTP mode and set the Authorization header to explore and test tools interactively.

Example request

Errors

A missing or invalid Authorization header fails the whole request with 401 Unauthorized, the same as the REST API. Once a request is authenticated, errors from an individual tool call (invalid parameters, 402 Payment Required for usage limits, upstream failures, and so on) are returned inside the MCP tool result with isError: true rather than as an HTTP failure — this lets the calling model see and react to the error instead of the whole request failing. The underlying status codes are the same ones described in Errors & Rate Limits.

Next steps