Home / MCP registry index / io.github.steffanricardo/the-dutch-directory
The Dutch Directory
io.github.steffanricardo/the-dutch-directory in the official MCP registry.
Endpoint https://thedutchdirectory.com/mcp-server/mcp.
The registry describes it as: Dutch-learning market map: schools, Verified Pro tutors, exams, paths and courses near any capital.
We read its 15 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
tdd_meta tdd_search tdd_shortlist tdd_tutors tdd_compare tdd_path tdd_stats tdd_graph tdd_move_plan tdd_employer_budget tdd_city_gaps tdd_death_watch tdd_conflict_ledger tdd_evidence_pack tdd_abroad
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-steffanricardo-the-dutch-directory)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.