Dutch Property Context
REMOTE · PROPERTY-CONTEXT.TRADEBRITE.NL · SCANNED OCT 4
Dutch property report by address: build year, energy label, neighbourhood, monument, schools.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 534 tokens (~534/item across 1 items; 1 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Dutch Property Context MCP server?
Dutch Property Context is a hosted endpoint at https://property-context.tradebrite.nl/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 · property-context.tradebrite.nl
claude mcp add --transport http nl-tradebrite-dutch-property-context 'https://property-context.tradebrite.nl/mcp'
{
"mcpServers": {
"nl-tradebrite-dutch-property-context": {
"url": "https://property-context.tradebrite.nl/mcp"
}
}
} {
"servers": {
"nl-tradebrite-dutch-property-context": {
"type": "http",
"url": "https://property-context.tradebrite.nl/mcp"
}
}
} [mcp_servers.nl-tradebrite-dutch-property-context] url = "https://property-context.tradebrite.nl/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nl-tradebrite-dutch-property-context": {
"type": "remote",
"url": "https://property-context.tradebrite.nl/mcp",
"enabled": true
}
}
} openclaw mcp add nl-tradebrite-dutch-property-context --url 'https://property-context.tradebrite.nl/mcp' --transport streamable-http
mcp_servers:
nl-tradebrite-dutch-property-context:
url: "https://property-context.tradebrite.nl/mcp" {
"McpServers": {
"nl-tradebrite-dutch-property-context": {
"Transport": "http",
"Url": "https://property-context.tradebrite.nl/mcp"
}
}
} assistant mcp add nl-tradebrite-dutch-property-context -t streamable-http -u 'https://property-context.tradebrite.nl/mcp'
{
"mcpServers": {
"nl-tradebrite-dutch-property-context": {
"type": "http",
"url": "https://property-context.tradebrite.nl/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
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 Oct 2026 · Probed https://property-context.tradebrite.nl/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tradebrite.nl | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 20234b26e604d80a0efce33c972c9663 |
| SANs: tradebrite.nl, property-context.tradebrite.nl, *.property-context.tradebrite.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 property-context.tradebrite.nl. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| nl. | present | 17153 | 13 | Verified |
| tradebrite.nl. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://property-context.tradebrite.nl/mcp | Verified | 200 | |
| http (plaintext) | http://property-context.tradebrite.nl/mcp | HTTPS enforced | 301 | https://property-context.tradebrite.nl/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 →
get_verified_property_context ~534
Geeft de geverifieerde context van een Nederlands woonadres uit officiële open bronnen: BAG (bouwjaar, oppervlakte, gebruiksdoel), CBS-buurtcijfers, RIVM (omgevingsgeluid, PM2.5, NO2), het geregistreerde energielabel, rijksmonumentstatus, ligging in een beschermd stads- of dorpsgezicht, en nabije scholen. Gebruik dit wanneer iemand vraagt naar feiten, risico's of omgeving van een Nederlands adres. Het antwoord heeft deze blokken: `identity` (welk pand is dit), `building` (bouwjaar, oppervlakte, gebruiksdoel), `energy`, `location`, `neighbourhood` (CBS), `environment` (geluid, PM2.5, NO2), `heritage` (rijksmonument), `protected_area` (beschermd stads- of dorpsgezicht, UNESCO-werelderfgoed), `schools`, `planning`, `signals` en `provenance`. Die eerste blokken bevatten feiten uit een bron; `provenance` vertelt per bron welke, wanneer opgehaald en met welke status. `signals` zijn observaties die nadrukkelijk GEEN gebrek vaststellen: bouwjaar 1921 betekent niet dat er loden leidingen zijn, het betekent dat dat geverifieerd moet worden. Een status `not_configured` of `unavailable` betekent dat wij het niet hebben opgehaald, niet dat het niet bestaat — vul zulke velden nooit zelf in met een schatting. Let in het bijzonder op `identity.match_verified`. Staat die op false, dan is het gevraagde adres niet teruggevonden en gaat de rest van het antwoord over een ander pand; meld dat dan aan de gebruiker in plaats van de gegevens te presenteren. Bij `identity.match_ambiguous` zijn er meerdere even goede kandidaten en staan die in `match_alternatives`. Dit is geen taxatie en geen juridisch of bouwkundig advies.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Nederlands adres, bij voorkeur met plaatsnaam of postcode, bijvoorbeeld 'Grote Markt 2, Haarlem' of '2011RD 2'. Zonder plaatsnaam is het resultaat vaak dubbelzinnig. |
| depth | string | – | Hoeveel detail. 'compact' (standaard) laat de bron-URL's en de volledige scholenlijst weg en is ongeveer de helft kleiner; alle feiten en álle signalen zitten er gewoon in. Vraag 'full' alleen als je… |
No output schema declared.
No examples provided.
What is the Dutch Property Context MCP server?
Dutch Property Context is an MCP server listed in the public MCP registry as nl.tradebrite/dutch-property-context. Dutch property report by address: build year, energy label, neighbourhood, monument, schools. This page covers its hosted endpoint (https://property-context.tradebrite.nl/mcp).
Is the Dutch Property Context MCP server safe to use?
Dutch Property Context 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 Dutch Property Context MCP server expose?
Dutch Property Context exposes 1 tool: get_verified_property_context. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.
Does the Dutch Property Context MCP server require authentication?
No. We connected to Dutch Property Context without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dutch Property Context MCP server still maintained?
Dutch Property Context is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.