Briefverzenden — fysieke post
REMOTE · WWW.BRIEFVERZENDEN.NL · SCANNED SEP 22
Verstuur een echte brief per post in 22 landen: lever een PDF aan, wij printen en posten hem.
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (bestellen). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 648 tokens (~129/item across 5 items; 5 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 Briefverzenden — fysieke post MCP server?
Briefverzenden — fysieke post is a hosted endpoint at https://www.briefverzenden.nl/api/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 · www.briefverzenden.nl
claude mcp add --transport http nl-briefverzenden-post 'https://www.briefverzenden.nl/api/mcp'
{
"mcpServers": {
"nl-briefverzenden-post": {
"url": "https://www.briefverzenden.nl/api/mcp"
}
}
} {
"servers": {
"nl-briefverzenden-post": {
"type": "http",
"url": "https://www.briefverzenden.nl/api/mcp"
}
}
} [mcp_servers.nl-briefverzenden-post] url = "https://www.briefverzenden.nl/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nl-briefverzenden-post": {
"type": "remote",
"url": "https://www.briefverzenden.nl/api/mcp",
"enabled": true
}
}
} openclaw mcp add nl-briefverzenden-post --url 'https://www.briefverzenden.nl/api/mcp' --transport streamable-http
mcp_servers:
nl-briefverzenden-post:
url: "https://www.briefverzenden.nl/api/mcp" {
"McpServers": {
"nl-briefverzenden-post": {
"Transport": "http",
"Url": "https://www.briefverzenden.nl/api/mcp"
}
}
} assistant mcp add nl-briefverzenden-post -t streamable-http -u 'https://www.briefverzenden.nl/api/mcp'
{
"mcpServers": {
"nl-briefverzenden-post": {
"type": "http",
"url": "https://www.briefverzenden.nl/api/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.
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 30 Aug 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.
- 28 Aug 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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Aug 26 0
- Schema quality: pass → fail ▼ functional
- “bestellen” reworded the description of “dubbelzijdig” cosmetic
- “prijs” reworded the description of “dubbelzijdig” cosmetic
- 11 Aug 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
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 0
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 22 Sept 2026 · Probed https://www.briefverzenden.nl/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.briefverzenden.nl | CN=YR1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 5a09ab1d5979817917efa82d9646ea5f963 |
| SANs: www.briefverzenden.nl | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.briefverzenden.nl. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| nl. | present | 17153 | 13 | Verified |
| briefverzenden.nl. | present | 64760 | 13 | Verified |
| www.briefverzenden.nl. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.briefverzenden.nl/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.briefverzenden.nl/api/mcp | HTTPS enforced | 308 | https://www.briefverzenden.nl/api/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 →
bestellen Bestelling aanmaken ~263
Maakt de bestelling aan en geeft een betaallink terug. De brief gaat pas de deur uit nadat de klant die link heeft betaald — geef de link dus aan de gebruiker en vraag hem af te rekenen. Vat eerst samen wat er verstuurd wordt.
| Name | Type | Req | Description |
|---|---|---|---|
| aangetekend | boolean | – | Aangetekend versturen; niet in elk land beschikbaar. |
| documentRef | string | yes | De verwijzing uit de tool document. Alleen een URL die die tool heeft teruggegeven. |
| dubbelzijdig | boolean | – | Beide zijden van het vel bedrukken. Standaard aan: het halveert het aantal vellen en houdt de brief vaker onder de volgende portoklasse. Zet op false voor enkelzijdig. |
| string | yes | E-mailadres van de klant, voor bevestiging en status. | |
| idempotencyKey | string | – | Verzin één unieke sleutel per bestelling, minstens 16 tekens (een UUID is prima), en hergebruik die bij opnieuw proberen. Voorkomt dubbele brieven. |
| kleur | boolean | – | In kleur drukken in plaats van zwart-wit. |
| ontvanger | object | yes | – |
| paginas | integer | yes | Aantal pagina’s, zoals document teruggaf. |
| speed | string | – | – |
No output schema declared.
No examples provided.
document Document aanleveren ~81
Levert de PDF aan die verstuurd moet worden, als base64 of als publieke https-URL. Geeft een verwijzing terug die je aan bestellen meegeeft, plus het getelde aantal pagina’s.
| Name | Type | Req | Description |
|---|---|---|---|
| fileBase64 | string | – | De PDF als base64. |
| fileUrl | string | – | Publieke https-URL waar de PDF staat. |
No output schema declared.
No examples provided.
landen Bestemmingslanden ~48
De landen waarheen een brief verstuurd kan worden, met per land of aangetekend beschikbaar is, of daar een handtekening bij hoort, en welke verzendtarieven er te kiezen zijn.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prijs Prijs berekenen ~189
Wat kost het versturen van een brief? Geef het aantal pagina’s en de bestemming. Het antwoord is de eindprijs inclusief printen, envelop en porto.
| Name | Type | Req | Description |
|---|---|---|---|
| aangetekend | boolean | – | Aangetekend versturen; niet in elk land beschikbaar. |
| dubbelzijdig | boolean | – | Beide zijden van het vel bedrukken. Standaard aan: het halveert het aantal vellen en houdt de brief vaker onder de volgende portoklasse. Zet op false voor enkelzijdig. |
| kleur | boolean | – | In kleur drukken in plaats van zwart-wit. |
| land | string | yes | Bestemmingsland in het Nederlands, bijv. "Duitsland". Zie de tool landen. |
| paginas | integer | yes | Aantal pagina’s van het document. |
| speed | string | – | Verzendtarief. Laat leeg voor het standaardtarief van dat land. |
No output schema declared.
No examples provided.
status Bestelling volgen ~67
Hoe ver is een verstuurde brief? Geef het sessie-id uit de betaallink of de referentie.
| Name | Type | Req | Description |
|---|---|---|---|
| referentie | string | – | De referentie uit de bevestiging. |
| sessie | string | – | Het session_id uit de betaallink (cs_live_…). |
No output schema declared.
No examples provided.
What is the Briefverzenden — fysieke post MCP server?
Briefverzenden — fysieke post is an MCP server listed in the public MCP registry as nl.briefverzenden/post. Verstuur een echte brief per post in 22 landen: lever een PDF aan, wij printen en posten hem. This page covers its hosted endpoint (https://www.briefverzenden.nl/api/mcp).
Is the Briefverzenden — fysieke post MCP server safe to use?
Briefverzenden — fysieke post scores 81 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 Briefverzenden — fysieke post MCP server expose?
Briefverzenden — fysieke post exposes 5 tools: landen, prijs, document, bestellen, status. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.
Does the Briefverzenden — fysieke post MCP server require authentication?
No. We connected to Briefverzenden — fysieke post without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Briefverzenden — fysieke post MCP server still maintained?
Briefverzenden — fysieke post is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.