slimwegdoen
REMOTE · SLIMWEGDOEN.NL
Where can your stuff go in the Netherlands? Advice per item and place, from selling to repair.
Available components
Last scanned (10 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 Security83
- 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 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 500 tokens (~166/item across 3 items; 3 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 Management10
- Stability observed for 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 74
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://slimwegdoen.nl/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=goedwegdoen.nl | CN=YE1,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 640ffdc693b63a281c0519a4c45f935e6ff |
| SANs: goedwegdoen.nl, slimwegdoen.nl, www.goedwegdoen.nl, www.slimwegdoen.nl | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of slimwegdoen.nl. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| nl. | DS published | 17153 | 13 | Verified |
| slimwegdoen.nl. | DS published | 50842 | 8 | Verified |
| slimwegdoen.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=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://slimwegdoen.nl/mcp | Verified | 200 | |
| http (plaintext) | http://slimwegdoen.nl/mcp | HTTPS enforced | 301 | https://slimwegdoen.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 →
grofvuil_in_gemeente Grofvuil in een gemeente ~80
Hoe grofvuil werkt in een Nederlandse gemeente: of de gemeente het ophaalt, wie dat doet, wat het kost, de voorwaarden en de link om een afspraak te maken, met de officiële bron. Plus de milieustraten in die gemeente.
| Name | Type | Req | Description |
|---|---|---|---|
| plaats | string | yes | Gemeente, woonplaats of postcode in Nederland. |
No output schema declared.
No examples provided.
plekken_in_de_buurt Plekken in de buurt ~126
Geeft de dichtstbijzijnde plekken van slimwegdoen.nl rond een plaats in Nederland, eventueel van één soort: kringloopwinkels, opkopers, repaircafés, weggeefplekken en goede doelen, of milieustraten. Met adres, afstand en of ze ophalen.
| Name | Type | Req | Description |
|---|---|---|---|
| plaats | string | yes | Woonplaats, gemeente, postcode of adres in Nederland, bijvoorbeeld 'Amersfoort', '3811' of 'Stationsplein 1, Zwolle'. |
| soort | string | – | Welk soort plek. Standaard alles. |
No output schema declared.
No examples provided.
waar_kan_dit_heen Waar kan dit heen? ~235
Geeft voor één voorwerp en een plek in Nederland het beste adres om het weg te doen, in de volgorde van de R-ladder (verkopen, weggeven, kringloop, repareren, recyclen, milieustraat). Gebruikt de gegevens van slimwegdoen.nl (5.800 kringloopwinkels, opkopers, repaircafés, goede doelen en milieustraten). Geeft het advies, twee alternatieven, de afstand, of ze ophalen, en hoe grofvuil in die gemeente werkt.
| Name | Type | Req | Description |
|---|---|---|---|
| plaats | string | yes | Woonplaats, gemeente, postcode of adres in Nederland, bijvoorbeeld 'Amersfoort', '3811' of 'Stationsplein 1, Zwolle'. |
| staat | string | – | goed = heel en bruikbaar; maken = werkt niet helemaal of is beschadigd, maar te repareren; kapot = niet meer te gebruiken. Standaard goed. |
| voorwerp | string | yes | Wat iemand kwijt wil, in gewone woorden, bijvoorbeeld 'driezitsbank', 'wasmachine', 'doos kinderkleding'. |
No output schema declared.
No examples provided.
How do I install the slimwegdoen MCP server?
slimwegdoen is a hosted endpoint at https://slimwegdoen.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 · slimwegdoen.nl
claude mcp add --transport http nl-slimwegdoen-slimwegdoen 'https://slimwegdoen.nl/mcp'
What is the slimwegdoen MCP server?
slimwegdoen is an MCP server listed in the public MCP registry as nl.slimwegdoen/slimwegdoen. Where can your stuff go in the Netherlands? Advice per item and place, from selling to repair. This page covers its hosted endpoint (https://slimwegdoen.nl/mcp).
Is the slimwegdoen MCP server safe to use?
slimwegdoen 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 slimwegdoen MCP server expose?
slimwegdoen exposes 3 tools: waar_kan_dit_heen, plekken_in_de_buurt, grofvuil_in_gemeente. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the slimwegdoen MCP server require authentication?
No. We connected to slimwegdoen without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the slimwegdoen MCP server still maintained?
slimwegdoen 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 slimwegdoen MCP server?
VerifyMCP ran 13 checks on slimwegdoen, 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.