MCP Server

The ERIP Gateway exposes a built-in MCP (Model Context Protocol) server at /mcp. AI agents — Claude Desktop, custom LLM workflows, or any MCP-compatible client — can call the same company search and detail endpoints as LLM-native tools, authenticated with the same API key used for the REST API.

Available Tools

search_companies

Searches the index and returns a JSON array of matching companies. Supply one of:

• name — partial company name, case-insensitive, minimum 4 characters
• lei — Legal Entity Identifier (LEI) code
• registrationNumber + countryCode — national registration number with ISO 3166-1 alpha-2 country code

Use the id field from the results as input to get_company_detail.

get_company_detail

Returns the full company detail document for a given id, including:

• Risk signals (covenant tightening, auditor language change, liquidity risk, going concern)
• Covenant monitoring data (thresholds, headroom, status, lender details)
• Ownership structure (parent/child company graph)
• Financial events (filings ingested, charges registered, director changes)
• Sentiment time series (social network and news sentiment scores)

Connect from Claude Desktop

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "elia-sephirot": {
      "type": "http",
      "url": "https://api.erip.io/mcp",
      "headers": {
        "X-Api-Key": "erip_YOUR_API_KEY"
      }
    }
  }
}

Replace erip_YOUR_API_KEY with the raw key returned when you create an API key.

Connect from a Custom Agent

Any MCP HTTP client can connect to the same endpoint. Pass the API key in the X-Api-Key header on every request:

POST /mcp
X-Api-Key: erip_YOUR_API_KEY
Content-Type: application/json

The server follows the standard MCP HTTP transport (JSON-RPC over HTTP with SSE for streaming).

Authentication

The MCP endpoint uses the same authentication as the REST API. Every connection attempt is validated against your API key before any tool call is processed. An invalid or missing key returns 401 Unauthorized.

See Authentication to register, log in, and create an API key.

Credits

Each tool call deducts credits from your account balance, using the same per-operation costs as the equivalent REST endpoint. If your balance is insufficient, the tool returns an error describing the cost and your remaining balance:

Insufficient credits. This operation costs 5 credits; 3 remaining.

Unlike the REST API, the MCP transport does not return X-Credits-Remaining or X-Credits-Cost headers — credit usage is visible in the error message on exhaustion and via GET /api/v1/auth/credits on the REST API.

Quick Start

1. Register — POST /api/v1/auth/register → receive a JWT token
2. Create an API key — POST /api/v1/auth/api-keys (Bearer JWT) → receive rawKey
3. Configure your MCP client — set url to https://api.erip.io/mcp and X-Api-Key to the raw key
4. Search — call search_companies with name="Heidelberg" → JSON array of matching companies
5. Detail — call get_company_detail with the id from step 4 → full risk intelligence document