Danmark Data
REMOTE · DATA.LYNBRO.DK
Danish companies (CVR), vehicles (DMR), addresses (DAR/BBR) and phone numbers. Live, read-only.
Available components
Last scanned (14 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: signatures are present but failed validation. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 956 tokens (~73/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +3
- HSTS header: fail → pass ▲ security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://data.lynbro.dk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lynbro.dk | CN=YE2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 63469ebb47c7c0c76b5859cc92d5a76e190 |
| SANs: *.lynbro.dk, lynbro.dk | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC bogus
Validation of data.lynbro.dk. — Bogus
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dk. | DS published | 16874 | 13 | Verified |
| lynbro.dk. | DS published | 54618 | 13 | Verified |
| data.lynbro.dk. | Bogus address RRset signature failed verification |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://data.lynbro.dk/mcp | Verified | 200 | |
| http (plaintext) | http://data.lynbro.dk/mcp | HTTPS enforced | 301 | https://data.lynbro.dk/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
address_report Address report: building, property value, flood risk ~71
Everything about a Danish address: administrative areas, BBR building data (year built, areas, use, heating), dwellings, official property valuation, zoning, coastal flood indicator and companies registered at the address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address id from search_address, or a free-text address |
Structured output declared, but exposes no named fields.
No examples provided.
cleanse_address Clean up a messy address ~70
Match a messy free-text address to the official one (datavask). Returns the best match, match category (A = exact, B = minor fix, C = uncertain) and the address id.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Address as typed by a person, with typos or missing parts |
Structured output declared, but exposes no named fields.
No examples provided.
company_financials Company annual accounts ~63
Key figures from the latest published annual reports (revenue, gross profit, profit before tax, result, assets, equity) in DKK, with a link to the filed report.
| Name | Type | Req | Description |
|---|---|---|---|
| cvr | string | yes | 8-digit CVR number |
Structured output declared, but exposes no named fields.
No examples provided.
company_people Company owners and management ~55
Owners (ejerregister), board, management, founders and auditors of a Danish company. Each participant has an 'enh' id that person_companies accepts.
| Name | Type | Req | Description |
|---|---|---|---|
| cvr | string | yes | 8-digit CVR number |
Structured output declared, but exposes no named fields.
No examples provided.
get_company Company details by CVR ~70
Full company profile from the CVR register: current name, status, founding date, address, industry, employees, production units, public contact details and VAT number.
| Name | Type | Req | Description |
|---|---|---|---|
| cvr | string | yes | 8-digit Danish CVR number, e.g. '24256790' (DK prefix allowed) |
Structured output declared, but exposes no named fields.
No examples provided.
person_companies Companies linked to a person ~52
All Danish companies a person is or was connected to (owner, board, management), plus bankruptcies of companies they were involved in.
| Name | Type | Req | Description |
|---|---|---|---|
| enh | integer | yes | Person 'enh' id from company_people |
Structured output declared, but exposes no named fields.
No examples provided.
phone_lookup Who owns this Danish phone number ~64
Identify a Danish phone number: operator, mobile/landline/service, region, companies that registered it in CVR, and a spam/trust verdict from user reports.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Danish number, 8 digits; spaces and +45 are fine |
Structured output declared, but exposes no named fields.
No examples provided.
phone_spam_check Is this number spam? ~41
Quick verdict for an incoming call: spam level, trust score, category and report count.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Danish number, 8 digits |
Structured output declared, but exposes no named fields.
No examples provided.
reverse_geocode Nearest address to coordinates ~44
Return the nearest official Danish address to a GPS position.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (WGS84) |
| lon | number | yes | Longitude (WGS84) |
Structured output declared, but exposes no named fields.
No examples provided.
search_address Search Danish addresses ~68
Search the official Danish address register (DAR). Returns address ids and coordinates. Pass an id to address_report for building and property data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Free text, e.g. 'Rådhuspladsen 1, København' |
Structured output declared, but exposes no named fields.
No examples provided.
search_companies Search Danish companies ~84
Find Danish companies in the CVR register by name. Returns CVR number, name, status, address, legal form and industry for each match. Use get_company for full details.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results |
| query | string | yes | Company name or part of it, e.g. 'Novo Nordisk'. A CVR number also works. |
Structured output declared, but exposes no named fields.
No examples provided.
vehicle_checks Vehicle checks: recalls, tax, insurance, inspections ~51
Before buying a used car: manufacturer recalls, owner tax, current insurer, inspection (syn) history, liens and valuations when available.
| Name | Type | Req | Description |
|---|---|---|---|
| plate_or_vin | string | yes | Danish number plate or VIN |
Structured output declared, but exposes no named fields.
No examples provided.
vehicle_lookup Vehicle by plate or VIN ~72
Vehicle data from the Danish Motor Register: make, model, variant, year, fuel, power, weights, status, first registration, leasing, inspection summary and odometer analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| plate_or_vin | string | yes | Danish number plate (e.g. 'AB12345') or VIN / stelnummer |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Danmark Data MCP server?
Danmark Data is a hosted endpoint at https://data.lynbro.dk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · data.lynbro.dk
claude mcp add --transport http dk-lynbro-danmark-data 'https://data.lynbro.dk/mcp'
What is the Danmark Data MCP server?
Danmark Data is an MCP server listed in the public MCP registry as dk.lynbro/danmark-data. Danish companies (CVR), vehicles (DMR), addresses (DAR/BBR) and phone numbers. Live, read-only. This page covers its hosted endpoint (https://data.lynbro.dk/mcp).
Is the Danmark Data MCP server safe to use?
Danmark Data scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Danmark Data MCP server expose?
Danmark Data exposes 13 tools: search_companies, get_company, company_people, company_financials, person_companies, and 8 more. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.
Does the Danmark Data MCP server require authentication?
No. We connected to Danmark Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Danmark Data MCP server still maintained?
Danmark Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Danmark Data MCP server?
VerifyMCP ran 13 checks on Danmark Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.