danish-cvr
# 🇩🇰 Danish CVR MCP Server
An MCP (Model Context Protocol) server that gives AI assistants access to the Danish company registry (CVR). Look up any Danish or Norwegian company by name, CVR number, phone, or production unit number.
## Why?
The MCP ecosystem has 500+ servers, but almost none cover Nordic/EU data sources. This is the first MCP server for Danish company data. Built for AI agents that need to research Danish businesses.
## Tools
| Tool | Description |
|------|-------------|
| `cvr_search` | Search by company name, CVR number, P-number, or phone |
| `cvr_lookup` | Direct lookup by 8-digit CVR number |
### Example queries
- "Look up Novo Nordisk" → Returns full company details, 33K employees, founded 1931
- "Find CVR 24256790" → Direct CVR lookup
- "Search for companies in Gilleleje" → Name-based search
- "Is CVR 12345678 bankrupt?" → Returns bankruptcy status
## Install
### Claude Desktop / OpenClaw
Add to your MCP config:
```json
{
"mcpServers": {
"danish-cvr": {
"command": "npx",
"args": ["-y", "mcp-danish-cvr"]
}
}
}
```
### Local development
```bash
git clone https://github.com/robobobby/mcp-danish-cvr
cd mcp-danish-cvr
npm install
npm start
```
## Data
Data comes from [cvrapi.dk](https://cvrapi.dk), a free API wrapping the official Danish CVR registry.
**Fields returned:** Company name, CVR number, address, industry (code + description), company type, employee count, phone, email, website, founding/closing date, owners, production units, bankruptcy status.
**Countries:** Denmark (`dk`) and Norway (`no`).
**Rate limit:** 50 free lookups per day per IP.
## Requirements
- Node.js 18+
- No API key needed
## License
MIT
TDQS
Scored across 2 tools
The two tools both return company details, and cvr_search supports lookup by CVR number, which overlaps with cvr_lookup's specific purpose. However, the descriptions clarify that cvr_lookup is for exact CVR lookups while cvr_search is broader, reducing some ambiguity.
Both tools follow the same cvr_<verb> pattern, using clear, consistent snake_case naming. The verb prefixes 'search' and 'lookup' are semantically appropriate.
With only two tools, the server feels thin for a registry API, but the two operations cover the core lookup scenarios. The count is borderline but not extreme.
Search by multiple identifiers and direct CVR lookup cover the primary read-only use cases for a public company registry. No mutating operations are expected, so the surface seems largely complete, though additional specialized queries could be added.