dk-regnskab-mcp

List published filings

list_filings

Read-onlyIdempotent

See which annual and interim reports a Danish company has filed with the Danish Business Authority, with PDF or XBRL document links, newest first. Check available years.

Instructions

List what a Danish company has filed with the Danish Business Authority (Erhvervsstyrelsen): annual reports, interim reports and their documents (PDF, XBRL), newest first. Use it to see which years are available or to get document links; use get_financials for the figures themselves. Returns an empty list for a CVR number with no filings (e.g. sole proprietorships). No paging: raise limit or set year to reach older filings.

Input Schema

TableJSON Schema

Name	Required	Description
`cvr`	Yes	Danish CVR number, 8 digits (spaces, dashes and a DK prefix are accepted), e.g. "24256790".
`year`	No	Only filings whose reporting period ends in this calendar year. Omit for all years.
`limit`	No	How many filings to return, newest first.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cvr`	Yes
`filings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.3.1Sep 26, 2026

changedInput schema / properties / cvr / description

Previous value: -"Danish CVR number, 8 digits (spaces, dashes and a DK prefix are accepted)."New value: +"Danish CVR number, 8 digits (spaces, dashes and a DK prefix are accepted), e.g. \"24256790\"."

changedInput schema / properties / limit / description

Previous value: -"How many filings to return."New value: +"How many filings to return, newest first."

addedInput schema / properties / year

Added value: +{
+  "description": "Only filings whose reporting period ends in this calendar year. Omit for all years.",
+  "maximum": 2100,
+  "minimum": 2012,
+  "type": "integer"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cvr": {
+      "type": "string"
+    },
+    "filings": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "correction": {
+            "description": "True when this filing corrects (omgørelse) an earlier one.",
+            "type": "boolean"
+          },
+          "cvr": {
+            "type": "string"
+          },
+          "documents": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "mimeType": {
+                  "type": "string"
+                },
+                "type": {
+                  "description": "e.g. AARSRAPPORT, AARSRAPPORT_ESEF, HALVAARSRAPPORT.",
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "mimeType",
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "periodEnd": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "periodStart": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "publishedAt": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Filing type; \"regnskab\" for financial reports.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "cvr",
+          "type",
+          "periodStart",
+          "periodEnd",
+          "publishedAt",
+          "correction",
+          "documents"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "cvr",
+    "filings"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond that: results are newest first, an empty list is returned for CVR numbers with no filings, and there is no paging, so callers should raise the limit or set a year to reach older filings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: it states the primary purpose first, then adds usage guidance, an edge case, and a pagination note. Every sentence contributes useful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what the tool returns, the main use cases, how it differs from a key sibling, empty-result behavior, and pagination limitations. Since an output schema exists, return value details are already covered structurally, so nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and every parameter already has a meaningful description in the schema. The tool description does not add much beyond what the schema states, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List') and a specific resource (filings with the Danish Business Authority), and enumerates the content (annual reports, interim reports, PDF, XBRL). It also distinguishes itself from the sibling get_financials by clarifying it returns filings and document links, not financial figures.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool: to see which years are available or get document links. It also names the alternative get_financials for figures, giving a clear when-not-to-use signal. Additional behavior around empty results and pagination further guides usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server