aria-mcp-cvr-dk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_companyA | Look up a Danish company in CVR (Det Centrale Virksomhedsregister) by CVR number, company name, or phone number. Returns structured fields: cvr, name, address, zipcode, city, phone, email, industry_code, industry_description, company_type, active status, start_date, end_date, employees, credit_bankrupt. Use this when you need to identify a company from an invoice, email, or contract, e.g. "hvem er CVR 12345678" or "find Netcompany". Data source: cvrapi.dk (free tier, ~50 lookups/day). |
| search_companiesA | Search for Danish companies by name in CVR (Det Centrale Virksomhedsregister). Note: cvrapi.dk returns a single best match per query, not a list of results. This tool returns that one match along with a note about this behaviour. For an exact lookup by CVR number use lookup_company instead. Data source: cvrapi.dk (free tier, ~50 lookups/day). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Both tools interact with the CVR register, but descriptions clearly differentiate: lookup_company accepts CVR number, name, or phone, while search_companies is specifically for name search and warns it returns only one match. Minor overlap exists since both can search by name, but the descriptions help agents choose correctly.
Both tool names follow the consistent verb_noun snake_case pattern: lookup_company and search_companies. No deviations or mixed conventions.
With only 2 tools, the server feels thin for a dedicated CVR lookup service. While the domain is narrow, a typical minimal set might include more variations (e.g., search by address or industry), so the count is borderline.
The server covers basic lookup and name search, but lacks other common operations like industry code lookup, paginated search, or filtering. Core functionality is present, but there are notable gaps for a comprehensive company registry tool.