Netherlands Rental Listings MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call requires one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_dutch_rental_listingsA | Search Kamernet, HousingAnywhere, and 11 Dutch anti-squat agency sites for one city, province, or the whole Netherlands. Returns one deduplicated list with rent, size, type, municipal registration status with the proving sentence, hide reasons, and new since last run flags. Detail pages and landlord message drafts on your own model key are optional. Pararius, Huurwoningen, Funda, and Gapph are not covered. Pay per event on Apify. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool there is no risk of misselection between siblings, and its purpose (aggregated multi-site rental search) is stated concretely. The only ambiguity is internal: detail-page fetching and landlord message drafting are folded into the same tool as optional modes rather than being separable actions.
The name follows a clear verb_noun pattern (search_dutch_rental_listings) and is domain-specific and readable. With a single tool there is no cross-tool pattern to verify, so consistency can only be judged in isolation.
A single tool for a multi-source aggregator is thin; the surface is borderline under-scoped. It does earn its place by bundling dedup, registration status, and optional detail/draft modes, but there is no way to split cheap search from expensive detail work.
Core search across many sources is covered, including dedup, hide reasons, and new-since-last-run flags, which is solid for a discovery workflow. However, there is no standalone listing-detail retrieval, saved-search management, or coverage for major sites (Pararius, Funda, Huurwoningen), leaving notable gaps.