Use Firmaradar from agents and automation

MCP — for AI agents

MCP (Model Context Protocol) is an open standard for how AI models connect to external data tools. Firmaradar's MCP server exposes 36 tools that let your agent look up companies, people, ownership structures, financials, announcements, risk/AML — and subscribe to industry monitoring — all with structured JSON responses and full type definitions.

Step 1 — Get the MCP server

The Firmaradar MCP server is published as Tiwas/firmaradar-mcp on GitHub (Apache 2.0). The MCP server is not yet published on PyPI / npm (not to be confused with n8n-nodes-firmaradar which is on npm — that is a separate n8n community node, not the MCP server). Clone the repo, create a venv, and install editable:

# Clone the public repo:
git clone https://github.com/Tiwas/firmaradar-mcp.git
cd firmaradar-mcp/python

# Create and activate a venv (PEP 668 blocks system pip on Debian/Ubuntu 23+):
python3 -m venv .venv
source .venv/bin/activate

# Install the package editable (pulls mcp/httpx/pydantic deps automatically):
pip install -e .

# Verify the console script is on PATH:
which firmaradar-mcp
# → ~/firmaradar-mcp/python/.venv/bin/firmaradar-mcp

Important: Note the absolute path that which firmaradar-mcp returns — you will use it in the MCP config below (not just python or firmaradar-mcp), because the agent client does not know about your venv without an absolute path.

If you see externally-managed-environment (Debian/Ubuntu 23+, PEP 668): the venv above solves this. Do not use --break-system-packages — the agent client may get confused about which Python is active.

Prefer to skip the local install? Remote MCP at mcp.firmaradar.no/mcp exposes the same tools over HTTP with OAuth — no Python, venv or absolute path to keep track of. Your client only needs the URL; see Step 3.

Step 2 — Create API key

Generate a key at My API keys. It is only shown once — copy it to a safe place before closing the dialog. Both env variables are required:

• FIRMARADAR_API_KEY — the key from the previous step
• FIRMARADAR_API_BASE — https://firmaradar.no (prod) or stage URL for testing

{
  "mcpServers": {
    "firmaradar": {
      "command": "<ABSOLUTT-STI>/firmaradar-mcp",
      "env": {
        "FIRMARADAR_API_KEY": "<din-nøkkel>",
        "FIRMARADAR_API_BASE": "https://firmaradar.no"
      }
    }
  }
}

claude mcp add-json firmaradar '{
  "command": "<ABSOLUTT-STI>/firmaradar-mcp",
  "env": {
    "FIRMARADAR_API_KEY": "<din-nøkkel>",
    "FIRMARADAR_API_BASE": "https://firmaradar.no"
  }
}'

claude mcp add firmaradar \
    -e FIRMARADAR_API_KEY=<din-nøkkel> \
    -e FIRMARADAR_API_BASE=https://firmaradar.no \
    -- <ABSOLUTT-STI>/firmaradar-mcp

# Verify the server is added + read:
claude mcp list
claude mcp get firmaradar

{
  "mcpServers": {
    "firmaradar": {
      "command": "<ABSOLUTT-STI>/firmaradar-mcp",
      "env": {
        "FIRMARADAR_API_KEY": "<din-nøkkel>",
        "FIRMARADAR_API_BASE": "https://firmaradar.no"
      }
    }
  }
}

[mcp_servers.firmaradar]
command = "<ABSOLUTT-STI>/firmaradar-mcp"
env = { FIRMARADAR_API_KEY = "<din-nøkkel>", FIRMARADAR_API_BASE = "https://firmaradar.no" }

{
  "mcpServers": {
    "firmaradar": {
      "command": "<ABSOLUTT-STI>/firmaradar-mcp",
      "env": {
        "FIRMARADAR_API_KEY": "<din-nøkkel>",
        "FIRMARADAR_API_BASE": "https://firmaradar.no"
      }
    }
  }
}

Step 4 — Verify the setup

Start a new agent session and ask «what Firmaradar tools do you have available?» The client should list 36 tools (all prefixed with firmaradar.). Then test one simple lookup, for example:

«Fetch basic information about Equinor (orgnr 923609016).»

If the client cannot find the server: check that the python package is installed in the same environment the client runs from (typical pyenv/conda problem), and that the log output from python -m firmaradar_mcp.server in the terminal shows «Server started».

Power Automate, Power Apps, Logic Apps and Copilot Studio

Firmaradar is published in Microsoft's official connector catalog as Firmaradar (Independent Publisher). So there is no custom connector to import yourself — Firmaradar sits in the standard connector list, and you connect with your own API key. It uses the same operation contract as the MCP server and the REST API, so a flow you build here returns the same fields an agent sees.

Availability and licensing

Premium means the user needs a license that covers premium connectors. The connector is available in all ordinary Power Platform and Logic Apps regions, but not in US Government (GCC and GCC High), US Department of Defense (DoD) or China Cloud operated by 21Vianet.

Step 1 — Get your API key

The connector authenticates with an API key — not OAuth. Microsoft only permits no-auth, Basic or API-key authentication for Independent Publisher connectors. The key is sent as the X-API-Key header on every call, exactly as against the REST API.

1. Create an account and sign in to Firmaradar.
2. Go to My page → My API keys and generate a new key. It is shown only once.
3. Store the key in a password vault or in Azure Key Vault — it grants the same access as your account.

Step 2 — Add Firmaradar to a flow

1. Open Power Automate (or Power Apps, Logic Apps or Copilot Studio) and create a new flow.
2. Choose “New step” and search for “Firmaradar” in the connector list.
3. Pick an action — for example Get full company profile.
4. The first time round you are asked to create a connection: paste the API key into the “Firmaradar API key” field and click “Create”.
5. Enter the organization number, for example 923609016 (Equinor ASA), and run the flow.

The response is structured JSON you can use straight away in the next step: post a risk alert to Teams, write a KYC record to Dataverse, or enrich a lead in your CRM. The fields are identical across MCP, n8n, Make and Power Platform, so a flow survives a change of platform.

Plugins — event-driven flow

"Plugin" in Firmaradar terminology is a webhook integration where we push data into your own system as soon as something happens (15-min cadence). You don't need to poll — Firmaradar notifies you when event types you have subscribed to hit.

Two subscription types

CRUD API for programmatic management

Both subscription types can be created/listed/updated/deleted via JSON API (authenticated with the same API key as the REST API):

# Create a NACE subscription (monitor section A in Oslo county)
curl -X POST -H "X-API-Key: $FIRMARADAR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "nace_code": "A",
       "fylke_filter": ["03"],
       "aggregation_mode": "real_time",
       "url": "https://din-server.no/firmaradar-webhook"
     }' \
     "https://firmaradar.no/api/v1/nace/subscriptions"

# List your subscriptions
curl -H "X-API-Key: $FIRMARADAR_API_KEY" \
     "https://firmaradar.no/api/v1/nace/subscriptions"

# Pause a subscription
curl -X PATCH -H "X-API-Key: $FIRMARADAR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"aktivert": false}' \
     "https://firmaradar.no/api/v1/nace/subscriptions/42"

Webhook delivery

• Firmaradar POSTs JSON to your url with Content-Type: application/json
• Optional signing (NACE): when the subscription has a signing_secret, every delivery is signed with X-Firmaradar-Signature (HMAC-SHA256 over the raw body, keyed with the signing_secret). Without a signing_secret, and for orgnr monitoring, deliveries are sent unsigned.
• Optional Authorization: Bearer <token> if you have set bearer_token
• Orgnr monitoring: up to 3 attempts on non-2xx responses, network errors or timeouts, with a few seconds' increasing pause between attempts. If all fail, the delivery is dropped and the monitoring's email recipients are notified (at most once a day).
• NACE industry monitoring: delivered at-least-once, digests included. Every request carries the header X-Firmaradar-Delivery-Id — stable per event and subscription (per batch for digests) and identical on every retry. Deduplicate on it, and respond quickly with a 2xx.
  • Failed attempts (non-2xx, timeout) are retried for as long as the subscription stays active and unchanged, with exponential backoff from 1 minute up to 6 hours. If we cannot connect, the delivery is retried in the next delivery round (about every 15 minutes, hourly for digests). Each attempt has a 30-second time budget, and redirects are not followed.
  • Pausing, deleting, or changing filters or aggregation stops pending deliveries. Events from before the subscription was created or re-enabled are not delivered retroactively.
  • Email digests enter a durable send queue after a final subscription check. The queue attempts delivery up to 8 times over about 36 hours. An email already queued is not withdrawn if the subscription is later paused or changed.
• 15-min cadence — you receive notification within 15 minutes after the event is registered at BRREG

When do you use what?

Security + compliance

• API keys are created per user, can be revoked at any time, and are rate-limited per tier.
• HMAC signing is optional for NACE webhooks: with a signing_secret, every delivery is signed (SHA-256 over the body). Orgnr deliveries are unsigned — verify them with the delivery_key (Bearer).
• Per-call DPA confirmation for AML/PEP screening — header X-FR-Purpose is required per call, and the audit log is retained for 60 months (Anti-Money Laundering Act § 30).
• Rate limits are enforced per key + per endpoint (e.g. AML screening is stricter: 50 calls / 30 min).
• PII tiering: standard / extended / compliance — see pricing for tier details.

Getting started

1. Create an account + log in at Firmaradar.no.
2. Choose tier on the pricing page.
3. Generate API key under My API keys.
4. For MCP: connect to mcp.firmaradar.no/mcp (OAuth) or clone Tiwas/firmaradar-mcp, set env vars, register in your agent client.
5. For plugins: create webhook subscriptions via UI (orgnr or NACE) or via JSON API.
6. Test against a known orgnr (e.g. 911 287 369 — BRREG) before going to prod.

Questions? Contact support or read the REST API documentation for endpoint details.