danish-cvr
Related Servers
Alternatives to danish-cvr
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search and retrieve Norwegian company data from the Brønnøysund Register Centre's open API, including company details, roles, and subunits.55 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to look up Danish phone numbers for operator, company (CVR), and spam/trust information using official open data.MIT
- AlicenseNot gradedqualityDmaintenanceProvides access to Norway's official business registry for searching companies, looking up organizational details, and identifying company roles and sub-units. It utilizes data from Brønnøysundregistrene to enable detailed queries by industry, municipality, or organization number.7 npmMIT
- AlicenseAqualityCmaintenanceEnables looking up Danish companies by CVR number, name, or phone via cvrapi.dk.2MIT
- AlicenseBqualityDmaintenanceEnables comprehensive access to the Norwegian Business Registry API for querying company information, board members, subsidiaries, organizational data, and voluntary organizations. Provides real-time access to over 1 million registered Norwegian entities with detailed corporate structure and governance data.155 npm8MIT
- AlicenseAqualityBmaintenanceThe company registry MCP: company data for AI agents, any country. One MCP server and REST API over national business registries — Norway (Brønnøysundregistrene / Enhetsregisteret, lookup by organisasjonsnummer/orgnr, VAT status) and the United Kingdom (Companies House, lookup by company number, accounts and confirmation-statement deadlines). Five tools: lookup_company, search_company, company_dea5MIT
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.