What is MCP

Model Context Protocol is an open standard by Anthropic that lets AI assistants safely call external tools. Our hosted server exposes the entire NeuralIndexer REST API as 20 typed tools, and the assistant picks the right one based on context.

Get an API token

There is no public token — every account has its own. Sign up and grab a token via one of the two paths below:

⚠️ Generating a new token immediately invalidates the previous one.

3 steps to AI-driven indexation

1. 1
   Register and get a token

   Via @InderixingBot ($0.38 bonus) or the email sign-up form ($0.05 test). Generate an API token in the cabinet.
2. 2
   Paste the hosted MCP URL into your client

   Copy a JSON snippet below for Claude Desktop / Cursor / Windsurf / ChatGPT, replace YOUR_API_TOKEN, restart the client.
3. 3
   Talk to your AI agent

   Ask the model to check balance, submit URLs or subscribe to a webhook. Cost-guard prevents accidental large charges.

Cursor

Open ~/.cursor/mcp.json or Settings → MCP → Add new MCP Server, paste the JSON below, replace YOUR_API_TOKEN and restart Cursor.

{
  "mcpServers": {
    "ivoque": {
      "url": "https://ivoque.de/mcp-rpc",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Claude Desktop

In Claude Desktop, open Settings → Connectors → Add custom connector:

Connector URL:    https://ivoque.de/mcp-rpc
Authentication:   OAuth → use "Bearer token"
Bearer token:     YOUR_API_TOKEN

Older Claude Desktop builds without the Connectors UI can use the local stdio variant.

Windsurf

Open ~/.codeium/windsurf/mcp_config.json and add:

{
  "mcpServers": {
    "ivoque": {
      "serverUrl": "https://ivoque.de/mcp-rpc",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

ChatGPT

Settings → Connectors → Custom connector:

Name:             NeuralIndexer
Description:      URL indexation in Google, Bing, Yandex
URL:              https://ivoque.de/mcp-rpc
Authentication:   Bearer token
Bearer token:     YOUR_API_TOKEN

Health-check

Verify connectivity from your machine before wiring the server into your client:

curl https://ivoque.de/mcp-rpc
# {"status":"ok","server":"@ivoque/mcp","transport":"streamable-http",...}

curl -X POST https://ivoque.de/mcp-rpc \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Account & Billing — 2 tools

Submissions — 8 tools

v2 (preferred)

v1 (legacy)

Indexation Checks — 4 tools

Webhooks — 6 tools

Subscribe to events submission.completed, check.completed, balance.changed. Each delivery is signed with HMAC-SHA256.

Safety guards

Example agent prompt

You say to the AI assistant:

I have 200 URLs from sitemap.xml.
Submit them via NeuralIndexer slow indexation,
set client_batch_id="weekly-2026-04-28" so reruns do not double-charge,
then subscribe my Make.com webhook https://hooks.example.com/done
to submission.completed and check.completed.
A few days later, list URLs from that submission that are not indexed yet.

What the agent does:

1. ivoque_check_balance — check the balance
2. ivoque_submit_v2 with queue:"slow", client_batch_id:"weekly-2026-04-28" and confirm_estimated_cost_usd:2.44 (200 × $0.0122)
3. ivoque_create_webhook with events:["submission.completed","check.completed"] — the receiver gets an HMAC secret for verification
4. Days later: ivoque_get_submission_links with only_status:"not_indexed" — a list of URLs to re-submit

Local stdio (advanced / offline)

Need to run the MCP server fully on your own machine — for air-gapped networks, low-latency batch jobs, or combining with other local-only tools? The same code is packaged as a stdio CLI.

{
  "mcpServers": {
    "ivoque": {
      "command": "node",
      "args": ["/absolute/path/to/ivoque-mcp/dist/index.js"],
      "env": { "IVOQUE_API_TOKEN": "YOUR_API_TOKEN" }
    }
  }
}

Source, build instructions and the npm tarball are available on request from @Inderixing (public npm release coming soon).

REST API without MCP

The same functionality is also exposed as a plain REST API — for CI/CD, dashboards, the WordPress plugin or integration into your own tools.