# io.bildata/bildata (remote · bildata.io)

Danish vehicle registration tax (registreringsafgift) calculator and DMR registration statistics

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `bildata.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-bildata-bildata/bildata.md), [page](https://verifymcp.io/servers/io-bildata-bildata/bildata)

## Channel facts

- Endpoint: `https://bildata.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2250 tokens (~375/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.bildata/bildata MCP server?

io.bildata/bildata is a hosted endpoint at https://bildata.io/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.

### Claude

```bash
claude mcp add --transport http io-bildata-bildata 'https://bildata.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-bildata-bildata": {
      "url": "https://bildata.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-bildata-bildata": {
      "type": "http",
      "url": "https://bildata.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-bildata-bildata]
url = "https://bildata.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-bildata-bildata": {
      "type": "remote",
      "url": "https://bildata.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-bildata-bildata --url 'https://bildata.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-bildata-bildata:
    url: "https://bildata.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-bildata-bildata": {
      "Transport": "http",
      "Url": "https://bildata.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-bildata-bildata -t streamable-http -u 'https://bildata.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-bildata-bildata": {
      "type": "http",
      "url": "https://bildata.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `calculate_registreringsafgift` (~996 tokens)

Calculate DANISH vehicle registration tax (registreringsafgift) for a new or used personbil, varebil or motorcykel under registreringsafgiftsloven. Same engine and validation as bildata.io's public calculator. Amounts in DKK; an estimate, not an official Motorstyrelsen valuation. REQUIRED PAIRS: condition="new" needs bruttovaerdi; condition="used" needs handelspris AND nypris (nypris is the used vehicle's own original price when new, not the new-vehicle price field). ALWAYS send co2 for a petrol, diesel or hybrid PERSONBIL or VAREBIL: an omitted co2 counts as 0 g/km, i.e. battery-electric, and makes the tax far too low with no error raised — zero on an ordinary car, and still only a fraction of the real figure on an expensive one. On motorcykel co2 does not select the drivetrain at all - isElectric does. Send every number as a JSON number (300000, not "300000"), use enum values exactly as listed, and OMIT an optional field you do not know rather than sending null.

Input parameters:

- `aaben` (boolean): Varebil only: open cargo bed (ladvogn)
- `actualKm` (number): Used: actual odometer km. The km regulation is skipped entirely unless actualKm, avgKm, vehicleAgeYears AND handelspris are all present.
- `allDealerListings` (boolean): Used: true only if EVERY comparable advert is a dealer listing (enables annoncefradrag + leveringsomkostninger)
- `avgKm` (number): Used: average odometer km of the comparable adverts. Part of the actualKm/avgKm/vehicleAgeYears set — a partial send is silently ignored.
- `bruttovaerdi` (number): New vehicles: REQUIRED when condition="new" (unused when condition="used"). Taxable value in DKK, i.e. price incl. VAT and margin BEFORE registration tax. NOT the advertised Danish showroom price, wh…
- `co2` (number): WLTP CO2 in g/km. PERSONBIL and VAREBIL: send it for any fuel-burning vehicle - an omitted value and an explicit 0 are BOTH read as battery-electric (EV phase-in and EV bundfradrag), which makes the…
- `condition` (string, required): new = first registration of a new vehicle; used = import/revaluation of a used vehicle
- `condition_stand` (string): Used: maintenance condition (vedligeholdelsesstand)
- `elForbrug` (number): Electric consumption in Wh/km. Send WITH elRaekkevidde — the battery deduction is (elForbrug/1000) * elRaekkevidde, so either one alone is a no-op.
- `elRaekkevidde` (number): Electric range in km (WLTP). Send WITH elForbrug — either one alone is a no-op.
- `handelspris` (number): Used vehicles: REQUIRED when condition="used". Current Danish trade price in DKK, incl. registration tax. Unused when condition="new".
- `isElectric` (boolean): MOTORCYKEL: the EV switch for that vehicle type. For personbil and varebil the drivetrain comes from co2 (0 or absent = electric), so this flag does not change the tax — but DO send it for a battery-…
- `nypris` (number): Used vehicles: REQUIRED when condition="used". The SAME vehicle's original price as new in DKK, incl. all taxes. Unused when condition="new" — for a new vehicle use bruttovaerdi.
- `targetYear` (number): Rules year to calculate under (default: current). A year with no published table silently falls back to the current rates; the answer's rules_year says which table actually applied.
- `totalvaegt` (number): Varebil only: total weight in kg
- `vehicleAgeYears` (number): Used: vehicle age in years since first registration. Also used on its own for the under-6-months rule, so send it even when you cannot supply the km set. The km regulation additionally needs actualKm…
- `vehicleType` (string, required): Vehicle category under Danish law

### `get_afgift_rates` (~84 tokens)

Machine-readable Danish vehicle registration tax rates 2026–2029: skalaknæk (brackets), CO2 tiers, bundfradrag and EV/plug-in phase-in (indfasning) percentages per year. Identical to GET https://bildata.io/api/afgift-prognose/rates. 2027–2029 rates are provisional.

### `forecast_registreringsafgift` (~447 tokens)

Project DANISH registration tax for a NEW vehicle across rules-years 2026–2029 (the EV/plug-in phase-in schedule changes the tax each year). Returns per-year results and deltas vs 2026. Amounts in DKK. Estimates, not official valuations. NEW vehicles only, and always the whole 2026-2029 span: for a USED import, or for a single year, use calculate_registreringsafgift instead. Send every number as a JSON number (300000, not "300000").

Input parameters:

- `aaben` (boolean): Varebil only: open cargo bed (ladvogn)
- `batteryCapacity` (number): Battery kWh (used with electricRange to derive Wh/km)
- `co2` (number): WLTP CO2 in g/km. PERSONBIL and VAREBIL: send it for any fuel-burning vehicle - an omitted value and an explicit 0 are BOTH read as battery-electric (EV phase-in and EV bundfradrag), which makes the…
- `electricConsumption` (number): Electric consumption Wh/km (overrides battery/range derivation)
- `electricRange` (number): Electric range km
- `isElectric` (boolean): MOTORCYKEL: the EV switch for that vehicle type, and on this tool the only reliable way to declare one - leave it unset with co2 omitted and the bike is priced as fuel-burning. For personbil and vare…
- `nypris` (number, required): Price as new in DKK (taxable value)
- `totalvaegt` (number): Varebil only: total weight in kg
- `vehicleType` (string, required): Vehicle category under Danish law

### `get_market_stats` (~235 tokens)

Danish new-vehicle registration statistics from bildata.io (weekly DMR data). Dimensions: fuel_type, brands (top 20), evs, imports (top imported makes), monthly_totals (last 12 months incl. leasing series), country_of_origin. kind=all covers every vehicle type; kind=Personbil passenger cars only. as_of is the data cutoff of the underlying extract — a month whose as_of is before month-end is PARTIAL. Market-level ONLY: the brands dimension is the top 20 brands and there is no per-model breakdown here — for a named MODEL use get_model_stats. It is NOT a way to get a brand total for a brand outside the top 20: a brand-only query there returns that brand's individual model rows (default 5, max 10, truncation disclosed in `note`) and defaults to kind=Personbil where this tool defaults to kind=all, so summing them does not reproduce a brand total from here.

Input parameters:

- `dimension` (string, required): Which slice to return; exactly one per call
- `kind` (string): Default: all

### `get_model_stats` (~298 tokens)

Look up Danish registration numbers for a SPECIFIC car model by name — e.g. "Tesla Model Y", "VW ID.4", "Skoda Enyaq". Covers every model since 2018. Use this when the question names a model or brand; get_top_models only covers the top sellers of one month, and get_market_stats only the top 20 brands. A model still selling returns period figures (this month, this year, last year, market share) plus all-time totals. A model with no registration in the last ~3 years returns ONLY lifetime totals and its first/last registration date — the period figures do not exist for it and are listed in `unavailableFields`; their absence is missing data, NOT zero sales. Spelling is forgiving (ID.4 = ID 4 = id4, Citroen = Citroën) and the response states which row it matched and how, so verify `name` before quoting the numbers.

Input parameters:

- `grouped` (boolean): Default true: trims collapsed into canonical models (Enyaq 85 -> Skoda Enyaq), matching bildata.io/stats. false returns raw registry variants.
- `kind` (string): Default: Personbil (passenger cars)
- `limit` (integer): Max matches to return, default 5
- `query` (string, required): Model or brand name, e.g. "Tesla Model Y" or "Toyota"

### `get_top_models` (~190 tokens)

Top-selling car models (and variants) in Denmark for a given month, from bildata.io's top-50 statistics (passenger cars, monthly, 12-month rolling window). Default: latest month, top 10. as_of is the data cutoff — if it is before month-end, the month is PARTIAL, not complete. A RANKING, bounded by the 12-month window. A model outside that month's top 50 is absent here — look that one up by name with get_model_stats. A month OLDER than the window cannot be answered by any tool on this server: get_model_stats reports fixed periods relative to today (this month, this year, last year, all-time), never an arbitrary past month.

Input parameters:

- `limit` (integer): Rows per list, default 10, max 50
- `month` (string): YYYY-MM; default latest available

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-bildata-bildata/bildata#diagnostics

## Score history

- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 66
- 2026-09-01: 65
- 2026-08-31: 65
- 2026-08-30: 65
- 2026-08-29: 64
- 2026-08-28: 64

## Common questions

### What is the io.bildata/bildata MCP server?

io.bildata/bildata is an MCP server listed in the public MCP registry as io.bildata/bildata. Danish vehicle registration tax (registreringsafgift) calculator and DMR registration statistics. This page covers its hosted endpoint (https://bildata.io/mcp).

### Is the io.bildata/bildata MCP server safe to use?

io.bildata/bildata scores 77 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 io.bildata/bildata MCP server expose?

io.bildata/bildata exposes 6 tools: calculate_registreringsafgift, get_afgift_rates, forecast_registreringsafgift, get_market_stats, get_model_stats, get_top_models. Their descriptions and schemas cost roughly 2,250 tokens of context every time the server is loaded.

### Does the io.bildata/bildata MCP server require authentication?

No. We connected to io.bildata/bildata without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.bildata/bildata MCP server still maintained?

io.bildata/bildata is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://bildata.io/mcp
- Website: https://bildata.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-bildata-bildata/bildata.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-bildata-bildata/bildata.json
- HTML version of this page: https://verifymcp.io/servers/io-bildata-bildata/bildata