MCP Server

Model Context Protocol

Plug any MCP-compatible AI client (Claude, ChatGPT's MCP integrations, custom agents) into EVE-KILL. 26 purpose-built tools cover killmail lookup, character intel, corp/alliance analytics, battle reports, Memgraph-backed relationship graphs, and route danger assessment. No API key. No auth. JSON-RPC over streamable HTTP.

Connect an AI client

MCP clients that speak streamable-HTTP can add EVE-KILL as a server. Endpoint: https://mcp.eve-kill.com/mcp (POST JSON-RPC, optional SSE on GET). Rate limit: 20 req/s per IP.

Claude Code / ChatGPT / native HTTP clients

{
  "mcpServers": {
    "evekill": {
      "type": "http",
      "url": "https://mcp.eve-kill.com/mcp"
    }
  }
}

Or from the CLI: claude mcp add --scope user --transport http evekill https://mcp.eve-kill.com/mcp

Claude Desktop (via mcp-remote)

{
  "mcpServers": {
    "evekill": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.eve-kill.com/mcp"
      ]
    }
  }
}

Desktop only supports stdio transport — the mcp-remote adapter proxies to HTTP. Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then fully quit + relaunch.

Raw cURL (sanity-check the server)

curl -s -X POST https://mcp.eve-kill.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search","arguments":{"query":"Jita"}}}'

Building an agent? Point it at /mcp.txt — a machine-readable usage guide tailored for AI models. MCP spec

Fetching tool list from https://mcp.eve-kill.com…