prometiam-risk-mcp

Model Context Protocol server for the Prometiam company data API — official company-registry data for Spain, France, the UK, Ireland, Poland and Norway, plus directors, corporate events, insolvency, VAT/LEI lookup and sanctions screening, as native MCP tools for Claude Desktop, Cursor, Continue, Cline, and any MCP-compatible client.

What you get

30 MCP tools that wrap the Prometiam Risk API:

Source: Spain (BORME), France (BODACC), United Kingdom (Companies House), Ireland (CRO), Poland (KRS), Norway (Brønnøysundregistrene / Enhetsregisteret, NLOD) — 26M+ companies. Daily updates. EU data residency.

Officer/director data is held for Spain, France, the UK and Norway. Ireland and Poland are company-level for now. Norway has no corporate-event stream, so the event tools return nothing for country=NO.

Install

npx -y prometiam-risk-mcp   # one-shot run, no install needed
# or
npm install -g prometiam-risk-mcp   # global install for the bin

Configure

You need a Prometiam API key. Free tier: 1,000 calls/month, no credit card. Sign up at https://www.prometiam.com/signup.

Set it as an environment variable:

export PROMETIAM_API_KEY="rk_live_..."

Use with Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "prometiam-risk": {
      "command": "npx",
      "args": ["-y", "prometiam-risk-mcp"],
      "env": {
        "PROMETIAM_API_KEY": "rk_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. The 30 tools appear in the tool list. Try:

"What's the Prometiam coverage today?" "Search for companies named Mercadona in Spain." "Run a sanctions screen on the name Juan Perez at threshold 85." "Build a corporate-event timeline for Inditex."

Use with Cursor

Edit .cursor/mcp.json in your project (or globally at ~/.cursor/mcp.json):

{
  "mcpServers": {
    "prometiam-risk": {
      "command": "npx",
      "args": ["-y", "prometiam-risk-mcp"],
      "env": {
        "PROMETIAM_API_KEY": "rk_live_your_key_here"
      }
    }
  }
}

Use with Continue

Add to ~/.continue/config.json under experimental.modelContextProtocolServers:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": ["-y", "prometiam-risk-mcp"],
          "env": { "PROMETIAM_API_KEY": "rk_live_your_key_here" }
        }
      }
    ]
  }
}

Use with any other MCP client

Anything that speaks MCP over stdio works. Run the binary with PROMETIAM_API_KEY set in the environment. JSON-RPC requests on stdin, responses on stdout, logs on stderr.

Environment variables

Smoke test

Once installed and configured, you can verify the server lists tools without spinning up an MCP client:

echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | PROMETIAM_API_KEY=rk_live_... npx -y prometiam-risk-mcp

You should see a JSON-RPC response with all 30 tools and their schemas.

Rate limits & pricing

Per Prometiam tier (returned in every response's meta.rate_limit):

Privacy and data residency

• All requests hit the Prometiam Risk API in EU (AWS eu-central-1, Frankfurt).
• The MCP server adds no telemetry of its own — it just forwards requests to the API.
• Officer data is processed under GDPR Article 6(1)(c) (legal obligation of public registries) and 6(1)(f) (legitimate interest in fraud prevention).
• Mostly read-only. The only mutating tools are monitor_subscribe and monitor_stop (create/delete a monitoring subscription tied to your key) and prospect_suppress (adds a GDPR opt-out); every other tool is read-only.

Source

This package is open source under the MIT license. The Risk API itself is a commercial service — see https://www.prometiam.com for terms.

• API documentation: https://www.prometiam.com/risk-api/docs
• OpenAPI 3.0 spec: https://www.prometiam.com/openapi.json
• Pricing: https://www.prometiam.com/pricing
• Support: https://www.prometiam.com/contact

License

MIT © Prometiam