Norric Intelligence MCP Server

Norric Intelligence MCP Server

Sweden's B2B intelligence infrastructure — exposed as a single MCP server.

Products: Norric SIGNAL · Norric Kreditvakt · Norric Vigil · SiteLoop · SigvikFramework: FastMCP 3.2.3 · Streamable HTTP transportTools: 21 tools across 5 products

Authentication

Every request to /mcp requires an API key — including the initializehandshake. Anonymous discovery is not supported.

Send the key in one of two headers (server accepts both; Authorization winswhen both are present):

X-Norric-Key:  <key>
Authorization: Bearer <key>

Working curl against the initialize endpoint:

curl -si https://mcp.norric.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Norric-Key: nrc_your_api_key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
       "params":{"protocolVersion":"2025-03-26","capabilities":{},
                 "clientInfo":{"name":"my-client","version":"1"}}}'
# → HTTP/1.1 200 OK
# → mcp-session-id: <id>     (use this header on subsequent calls in the session)

Missing key returns 401 {"error": "Missing API key…"}.Wrong key returns 401 {"error": "Invalid API key…"}.

Get a key: https://norric.io/api

Pricing

Standard and Compliance tiers are issued direct — email [email protected] for qualification,pricing, and ToS. Public self-serve for paid tiers is paused pending kreditupplysningslagen(KuL) review for the Kreditvakt offering.

Connect

Claude Code (CLI)

claude mcp add norric https://mcp.norric.io/mcp \
  --header "Authorization: Bearer nrc_your_api_key"

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json)

{
  "mcpServers": {
    "norric": {
      "url": "https://mcp.norric.io/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer nrc_your_api_key"
      }
    }
  }
}

Cursor / Windsurf (.cursor/mcp.json)

{
  "mcpServers": {
    "norric": {
      "url": "https://mcp.norric.io/mcp",
      "headers": {
        "Authorization": "Bearer nrc_your_api_key"
      }
    }
  }
}

Local development

python server.py
# Server starts at http://localhost:8080/mcp
claude mcp add norric http://localhost:8080/mcp \
  --header "Authorization: Bearer nrc_your_api_key"

Tools

Norric SIGNAL — Municipal procurement intelligence

Norric Kreditvakt — Insolvency intelligence

Norric Vigil — Company lifecycle detection

SiteLoop — Website pipeline

Sigvik — BRF property intelligence

Cross-portfolio

Response envelope

Every tool returns the same structure:

{
  "data": { ... },
  "metadata": {
    "response_id": "nrsp_abc123",
    "tool": "tool_name_v1",
    "source": ["skatteverket", "bolagsverket"],
    "fetched_at": "2026-04-26T10:00:00Z",
    "confidence": 0.91,
    "cache_ttl_seconds": 3600
  },
  "signals": [
    {
      "key": "skuld_published",
      "label": "Skatteskuld publicerad",
      "value": true,
      "weight": 0.45,
      "direction": "risk",
      "source": "skatteverket"
    }
  ],
  "warnings": []
}

metadata.confidence (0-1): how much to trust the datametadata.cache_ttl_seconds: how long before re-fetchingsignals[]: always present, empty list if not applicable

Two-step handshake

MCP requires initializing a session before calling tools:

# Step 1: Initialize (no auth required)
SESSION=$(curl -si \
  -X POST https://mcp.norric.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1"}}}' \
  | grep -i "mcp-session-id" | awk '{print $2}' | tr -d '\r')

# Step 2: Call a tool (auth required)
curl -s -X POST https://mcp.norric.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer nrc_your_api_key" \
  -H "mcp-session-id: $SESSION" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"norric_status_v1","arguments":{}}}'

Current status

Tools are live and callable. Ingestion pipelines are the next build step —connect each product's data source to activate live scoring.

Check live status: call norric_status_v1.

Deploy to Railway

# MCP server service (existing — daring-adaptation or similar):
# Start command: python server.py
# Env vars:
#   PORT=8080
#   NORRIC_API_KEYS=<hash:tier:label lines>
#   SUPABASE_URL=<your supabase url>
#   SUPABASE_KEY=<your supabase anon key>

# Key issuance service (separate Railway service):
# Start command: uvicorn issuance.main:app --host 0.0.0.0 --port $PORT
# Env vars: STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRICE_*,
#           SENDGRID_API_KEY, RAILWAY_API_TOKEN, RAILWAY_SERVICE_ID

Registry

• mcp.so listing: registry/mcpso_listing.md
• Anthropic connector directory: registry/anthropic_connector_submission.md

Norric AB · Malmö · 2026