Living in the Netherlands
REMOTE · NLTAXCALCULATOR.NL
Living in NL: legal max rent (points), car by plate (RDW), city budget, current fees with sources.
Available components
Last scanned (11 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 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: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1158 tokens (~165/item across 7 items; 4 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +3
- Schema quality: 250 → 165 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: 100 functional
- New prompt “settling_into_a_city” functional
- New resource “city-costs” functional
- New resource “current-facts” functional
- New resource “rent-rules” functional
- Server version: 0.1.0 → 0.2.0 functional
- 31 Oct 26 70
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 5 Nov 2026 · Probed https://nltaxcalculator.nl/dutch-tax/api/living/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nltaxcalculator.nl | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f2712dada95ef1a213bd4b869d6b86ee |
| SANs: nltaxcalculator.nl, *.nltaxcalculator.nl | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nltaxcalculator.nl. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| nl. | DS published | 17153 | 13 | Verified |
| nltaxcalculator.nl. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://pagead2.googlesyndication.com https://*.googlesyndication.com https://*.google.com https://*.googleadservices.com https://*.doubleclick.net https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; font-src 'self'; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://*.googlesyndication.com https://*.google.com https://*.doubleclick.net https://*.adtrafficquality.google https://challenges.cloudflare.com https://opendata.rdw.nl; img-src 'self' data: blob: https://flagcdn.com https://i.ytimg.com https://*.googlesyndication.com https://*.google.com https://*.gstatic.com https://*.doubleclick.net; frame-src 'self' https://googleads.g.doubleclick.net https://tpc.googlesyndication.com https://pagead2.googlesyndication.com https://*.google.com https://*.googlesyndication.com https://*.adtrafficquality.google https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nltaxcalculator.nl/dutch-tax/api/living/mcp | Verified | 200 | |
| http (plaintext) | http://nltaxcalculator.nl/dutch-tax/api/living/mcp | HTTPS enforced | 301 | https://nltaxcalculator.nl/dutch-tax/api/living/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 →
car_by_plate Dutch car lookup by number plate (RDW) ~156
Looks up a Dutch-registered car by its number plate (kenteken) in the official RDW register: make, model, first registration, fuel, CO2 emission, catalogue price, empty weight, when the periodic inspection (APK) is due and whether it is insured. With a taxable income it also gives the company car tax (bijtelling) for 2026, including the electric-car rate locked for 60 months from first registration. Live data from RDW Open Data.
| Name | Type | Req | Description |
|---|---|---|---|
| plate | string | yes | Dutch number plate, with or without dashes, e.g. AB-123-C |
| taxable_income | number | – | Taxable income per year before the bijtelling, for the company car tax (optional) |
No output schema declared.
No examples provided.
monthly_budget_by_city Monthly budget in a Dutch city: net pay minus rent and fixed costs ~274
What is left each month in a Dutch city: net salary (2026 tax, optional 30% ruling and holiday allowance) minus a typical unregulated-sector rent for the home size in that city, the basic health insurance premium (less any healthcare allowance), an average energy bill and the municipal charges for a renter. Cities with their own figures: Amsterdam, Amstelveen, Haarlem, The Hague, Rotterdam, Utrecht, Eindhoven, Helmond, Leeuwarden, Zwolle; any other city uses the national average rent and leaves out municipal charges. Food, transport, internet and water board charges are not included.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | number | – | Adults in the household (each pays health insurance). Default 1. |
| city | string | – | City. Default other (national average). |
| gross_annual | number | yes | Gross yearly salary in euros, without holiday allowance |
| holiday_allowance | boolean | – | Gets 8% holiday allowance (spread over 12 months here). Default true. |
| home_size_m2 | number | – | Size of the rented home in m². Default 60. |
| monthly_rent | number | – | Actual monthly rent if known, instead of the city average (optional) |
| thirty_percent_ruling | boolean | – | Has the 30% ruling. Default false. |
No output schema declared.
No examples provided.
nl_current_facts Current Dutch figures with their source (2026) ~187
Current Dutch amounts that change every year, each with the period it applies to and its official source, so an answer does not rely on outdated knowledge. Topics: health_deductible (Healthcare deductible (eigen risico)), child_benefit (Child benefit (kinderbijslag)), passport_id_fees (Passport and identity card fees), ind_fees (IND application fees (residence permits and naturalisation)), rent_limits (Rent limits and maximum rent increases), minimum_wage (Minimum wage (wettelijk minimumloon)). Ask by topic, or with a short question. For income tax figures use the tax server's dutch_tax_figures tool.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | A short question or keywords, e.g. "passport cost" or "kinderbijslag" (used when no topic is given) |
| topic | string | – | One of the topics |
No output schema declared.
No examples provided.
rent_points_check Dutch rent points check: legal maximum rent and allowed increase ~244
For a rented independent home (zelfstandige woning: own front door, kitchen and toilet) in the Netherlands: from its points under the points system (woningwaarderingsstelsel, WWS), the rental sector (social up to 143 points, regulated mid-rent up to 186, free sector above), the legal maximum basic monthly rent (kale huur) for 2026, whether a current rent is above it, and the maximum yearly rent increase for that sector. The points come from the government's Huurprijscheck on huurcommissie.nl. Rooms (onzelfstandige woonruimte) use a different table and are not covered.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_start | string | – | Start date of the rental contract, YYYY-MM-DD (optional; mid-rent limits apply to contracts from 1 July 2024) |
| current_rent | number | – | Current basic monthly rent (kale huur, without service costs) in euros (optional) |
| points | number | yes | Points of the home under the points system (from the Huurprijscheck) |
| proposed_increase_pct | number | – | A rent increase the landlord proposed, in % (optional) |
No output schema declared.
No examples provided.
How do I install the Living in the Netherlands MCP server?
Living in the Netherlands is a hosted endpoint at https://nltaxcalculator.nl/dutch-tax/api/living/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 · nltaxcalculator.nl
claude mcp add --transport http nl-nltaxcalculator-living-nl 'https://nltaxcalculator.nl/dutch-tax/api/living/mcp'
What is the Living in the Netherlands MCP server?
Living in the Netherlands is an MCP server listed in the public MCP registry as nl.nltaxcalculator/living-nl. Living in NL: legal max rent (points), car by plate (RDW), city budget, current fees with sources. This page covers its hosted endpoint (https://nltaxcalculator.nl/dutch-tax/api/living/mcp).
Is the Living in the Netherlands MCP server safe to use?
Living in the Netherlands scores 75 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 Living in the Netherlands MCP server expose?
Living in the Netherlands exposes 4 tools: car_by_plate, monthly_budget_by_city, nl_current_facts, rent_points_check. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.
Does the Living in the Netherlands MCP server require authentication?
No. We connected to Living in the Netherlands without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Living in the Netherlands MCP server still maintained?
Living in the Netherlands is still listed as active in the MCP registry. We last reached this channel on 5 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 Living in the Netherlands MCP server?
VerifyMCP ran 13 checks on Living in the Netherlands, 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.