NeuralVerge MCP Server

An MCP (Model Context Protocol) server that wraps the full NeuralVerge API — AI Research, AI Extract, AI Agents, and Data Sources (LinkedIn, Crunchbase, Email enrichment and lookup, Phone enrichment and lookup, Email verification) — as MCP tools, so any MCP-compatible client (Claude Desktop, Claude Code, Cursor, ChatGPT/GPT clients with MCP support, and others) can call it directly.

This is an independent, unofficial wrapper around the NeuralVerge API. It is not affiliated with or endorsed by NeuralVerge.

Getting an API key

Before installing, you need a NeuralVerge account and an API key:

1. Sign up at app.neuralverge.ai (or via neuralverge.ai → "Get started").

2. Choose a plan (see Pricing below) — this determines your monthly points allowance.

3. Generate an API key from your account/API settings in the app.

4. Use that key as NEURALVERGE_API_KEY in the Configuration step further down.

Related MCP server: Mixpeek MCP Server

Tools

Every NeuralVerge API endpoint is exposed as a 1:1 MCP tool. run_research and run_agent are asynchronous — they return a session_id immediately; call get_session_status every 2–5 seconds until status is complete or failed (NeuralVerge's own polling guidance). Every other tool returns its result synchronously.

AI Research

run_research

Starts the full multi-step research workflow: searches, analyzes sources, and returns a structured report. Async — returns a session_id.

Cost: 20–400 pts, depending on deepsearch_model depth tier.

run_agent

Runs a saved NeuralVerge agent — a reusable workflow with baked-in instructions and settings — by its agentId. Async — returns a session_id.

Cost: same tiered pricing as run_research, based on the agent's configured depth.

get_session_status

Polls a session created by run_research or run_agent.

Returns status (queued/running/complete/failed) and, once complete, a results object with a human (Markdown summary) and machine (structured JSON) field. Polling itself is free.

run_search

Runs a synchronous web search and returns ranked results (title, URL, snippet). No polling needed.

Cost: 5 pts.

AI Extract

run_extract

Loads a page by URL and extracts structured data according to natural-language instructions and/or a JSON schema. Synchronous.

Cost: 5 pts.

This is also the generic gateway NeuralVerge itself uses for every catalog data source that doesn't have its own dedicated endpoint (corporate registries, review sites, LinkedIn profiles without email) — point it at the right URL with the right extract_schema_json and it behaves like a dedicated source. See Data sources not exposed as dedicated tools below.

AI Agents

run_agent (see above, under AI Research) — NeuralVerge tags it "AI Agents" since it executes saved, reusable agent configurations rather than one-off instructions.

Data Sources — dedicated tools

These 11 catalog sources have their own dedicated endpoints/tools:

run_linkedin_email

LinkedIn profile lookup by URL, returning contact details including email when available (catalog: LinkedIn people profile + Email).

Cost: 10 pts.

run_linkedin_domain

Finds a LinkedIn profile from a company name/domain plus a full name (catalog: LinkedIn profile by name and domain).

Cost: 10 pts.

run_linkedin_company_search

Searches LinkedIn companies by query with optional filters.

Cost: 5 pts per company returned.

run_linkedin_people_search

Searches LinkedIn people with an optional free-text query and advanced filters (company, title, seniority, industry, experience, location).

Cost: 100 pts per 25 results.

run_linkedin_company_employee

Searches employees of one or more given companies, using the same filter set as run_linkedin_people_search.

Cost: 30 pts per run + 5 pts per profile returned.

run_email_enrichment

Enriches a known email with profile data (name, phones, company, position, LinkedIn/X/Telegram, work experience).

Cost: 10 pts.

run_email_validation

Validates deliverability of an email address (valid/invalid/risky, catch-all detection, mail provider, confidence).

Cost: 1 pt — the cheapest call in the catalog.

run_email_finder

Finds a professional email address from a company domain, first name, and last name.

Cost: 10 pts.

run_phone_enrichment

Enriches a known phone number with profile data (name, emails, company, LinkedIn/X/Telegram, carrier), worldwide.

Cost: 10 pts.

run_phone_enrichment_us

Validates and enriches a US phone number specifically: carrier, line type, activity score, litigator risk, and owner records (with addresses).

Cost: 100 pts.

run_crunchbase_company

Fetches structured company data from a Crunchbase organization URL (website, location, founding year, employees, industries, funding, description).

Cost: 15 pts.

Data sources not exposed as dedicated tools

NeuralVerge's catalog lists 29 data sources in total. The 11 above have dedicated endpoints/tools. The other 18 are all reached through run_extract — pass the source's own page URL as url and a matching extract_schema_json; the "Read more" page for each source on the catalog site has the exact schema and an example curl call. All of them cost 5 pts (the standard run_extract price), except where noted.

Company intelligence

Corporate registry (official company registers, by country)

Social media (LinkedIn, without a dedicated tool)

Example: fetching a UK company record via run_extract:

{
  "url": "https://find-and-update.company-information.service.gov.uk/company/08804411",
  "instructions": "Extract data from Companies House profile",
  "settings": {
    "country_code": "us",
    "extract_schema_json": "{ ... }"
  }
}

Pricing

NeuralVerge uses simple, points-based pricing — one pool of points covers research, extraction, and every data source. See neuralverge.ai/pricing for the current numbers.

Plans

Action costs

AI research depth tiers

Plans can be changed anytime; the new points allowance applies on the next billing cycle. Points reset every cycle.

Requirements

• Node.js >= 18

• A NeuralVerge API key (Bearer token) — see Getting an API key above and docs.neuralverge.ai/authentication

Installation

npm install
npm run build

This compiles TypeScript sources in src/ to dist/.

Configuration

The server reads its configuration from the environment:

Copy .env.example to .env for local reference, but note the server itself reads process environment variables — most MCP clients pass these via their own config, not via a .env file.

Transports & client compatibility

This server implements both MCP transports, selected via MCP_TRANSPORT, because different clients require different ones:

stdio (Claude Desktop, Claude Code, Cursor)

These clients spawn the server as a local subprocess and talk JSON-RPC over its stdin/stdout — no networking involved. Add this to your client's MCP config (claude_desktop_config.json for Claude Desktop, .cursor/mcp.json for Cursor — the shape is identical):

{
  "mcpServers": {
    "neuralverge": {
      "command": "node",
      "args": ["/absolute/path/to/MCP/dist/index.js"],
      "env": {
        "NEURALVERGE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Streamable HTTP (ChatGPT / remote clients)

ChatGPT's MCP connectors only accept remote servers over Streamable HTTP or SSE — they cannot launch a local node/npx process the way Claude Desktop and Cursor do. To use this server from ChatGPT, run it in HTTP mode and make it reachable over HTTPS:

MCP_TRANSPORT=http MCP_HTTP_PORT=8787 MCP_HTTP_AUTH_TOKEN=some_shared_secret \
NEURALVERGE_API_KEY=your_api_key_here node dist/index.js

This starts a stateless Streamable HTTP server (fresh MCP session per request, no server-side session storage) at http://localhost:8787/mcp, plus a GET /health check. To reach it from ChatGPT you need a public HTTPS URL — either:

• deploy it to any Node host (Fly.io, Render, a VPS, a container platform, etc.), or

• tunnel your local instance for testing (e.g. ngrok http 8787 or a Cloudflare Tunnel).

Then in ChatGPT: enable Developer Mode (Settings → Connectors → Advanced), add a connector pointing at https://your-host/mcp, and set the Authorization: Bearer <MCP_HTTP_AUTH_TOKEN> header if you set one.

Security note: NEURALVERGE_API_KEY lives on the server and is shared by everyone who can reach the HTTP endpoint — it is not per-ChatGPT-user. Always set MCP_HTTP_AUTH_TOKEN (or put the server behind your own auth) before exposing it publicly; otherwise anyone with the URL can spend your NeuralVerge points.

Manual testing

You can exercise the server with the official MCP Inspector:

NEURALVERGE_API_KEY=your_api_key_here npm run inspector

The Inspector's "HTTP" connection mode also works against the http transport (point it at http://localhost:8787/mcp), which is a convenient way to sanity-check the ChatGPT-facing path without a real ChatGPT connector.

Error handling

The NeuralVerge API returns these status codes, which this server surfaces as MCP tool errors with a descriptive message:

Project structure

src/
  client.ts   # thin fetch wrapper: auth header, error mapping
  tools.ts     # all 16 MCP tool definitions (input schemas + handlers)
  index.ts     # MCP server bootstrap (stdio transport, or Streamable HTTP if MCP_TRANSPORT=http)

License

MIT — see LICENSE.