klusvang-public
Registry code: 4229fedf62fd1b07
Public, read-only Klusvang data: counts of building-permit notices (omgevingsvergunningen) published by Dutch municipalities, per municipality, province, work type and month. Counts only: there are no addresses, names or single permits here. Call find_municipality to get a municipality slug. Every answer has a klusvang.nl url and a source line: cite Klusvang and give the url. Small counts (1 to 4) for one municipality are shown as "fewer than 5".
- endpoint
- https://klusvang.nl/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is klusvang-public live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is klusvang-public free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does klusvang-public have?
- 5 tools: municipality_permit_counts, province_permit_counts, work_type_nationwide, find_municipality, bouwmonitor_month.
- Is klusvang-public safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
bouwmonitor_month open 8h ago
The Klusvang bouwmonitor: a frozen monthly count of building-permit notices in the Netherlands, by work type and province, with a ranking of municipalities (optionally for one work type or one province). Without month: the latest closed month. Closed months never change. Counts only.
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Municipalities in the ranking. Default 20." }, "month": { "type": "string", "pattern": "^\\d{4}-\\d{2}$", "description": "YYYY-MM. Default: the latest closed month." }, "province": { "enum": [ "groningen", "friesland", "drenthe", "overijssel", "flevoland", "gelderland", "utrecht", "noord-holland", "zuid-holland", "zeeland", "noord-brabant", "limburg" ], "type": "string", "description": "Rank only the municipalities of this province." }, "work_type": { "enum": [ "nieuwbouw", "aanbouw", "verbouwing", "kozijnen", "dakkapel", "dakwerk", "verduurzaming", "warmtepomp", "zonnepanelen", "functiewijziging", "bedrijfspand", "terrein", "sloop", "kap" ], "type": "string", "description": "Rank municipalities by this work type." } }, "additionalProperties": false }arguments 55 linesmunicipality_permit_counts unknown 8h ago
How many building-permit notices (omgevingsvergunningen) one Dutch municipality published recently: the last 60 and 30 days, the 30 days before, new applications, recent grants, a breakdown by work type, and its total and national rank in the latest closed month of the Klusvang bouwmonitor. Counts only: no addresses, names or single permits.
{ "type": "object", "required": [ "municipality" ], "properties": { "work_type": { "enum": [ "nieuwbouw", "aanbouw", "verbouwing", "kozijnen", "dakkapel", "dakwerk", "verduurzaming", "warmtepomp", "zonnepanelen", "functiewijziging", "bedrijfspand", "terrein", "sloop", "kap" ], "type": "string", "description": "Work type, e.g. dakkapel (dormer), aanbouw (extension), kozijnen (window frames)." }, "municipality": { "type": "string", "pattern": "^[a-z0-9-]{1,100}$", "description": "Municipality URL slug, e.g. nijmegen or s-hertogenbosch. Use find_municipality to get it." } }, "additionalProperties": false }arguments 34 linesprovince_permit_counts unknown 35h ago
Building-permit notices in one Dutch province in the last 60 and 30 days, by work type, with the municipalities that published the most. Counts only.
{ "type": "object", "required": [ "province" ], "properties": { "province": { "enum": [ "groningen", "friesland", "drenthe", "overijssel", "flevoland", "gelderland", "utrecht", "noord-holland", "zuid-holland", "zeeland", "noord-brabant", "limburg" ], "type": "string", "description": "Province URL slug, e.g. gelderland or noord-holland." }, "work_type": { "enum": [ "nieuwbouw", "aanbouw", "verbouwing", "kozijnen", "dakkapel", "dakwerk", "verduurzaming", "warmtepomp", "zonnepanelen", "functiewijziging", "bedrijfspand", "terrein", "sloop", "kap" ], "type": "string", "description": "Work type, e.g. dakkapel (dormer), aanbouw (extension), kozijnen (window frames)." } }, "additionalProperties": false }arguments 47 lineswork_type_nationwide unknown 35h ago
One work type (e.g. dakkapel, aanbouw, kozijnen) across all Dutch municipalities: notices in the last 60 and 30 days, its share and rank among work types, per province, and the municipalities with the most. Counts only.
{ "type": "object", "required": [ "work_type" ], "properties": { "work_type": { "enum": [ "nieuwbouw", "aanbouw", "verbouwing", "kozijnen", "dakkapel", "dakwerk", "verduurzaming", "warmtepomp", "zonnepanelen", "functiewijziging", "bedrijfspand", "terrein", "sloop", "kap" ], "type": "string", "description": "Work type, e.g. dakkapel (dormer), aanbouw (extension), kozijnen (window frames)." } }, "additionalProperties": false }arguments 29 linesfind_municipality unknown 8h ago
Find the URL slug of a Dutch municipality (gemeente) by name, for the other tools. Returns at most 10 matches with their province and the Klusvang page.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 80, "description": "Part of the name, e.g. Den Bosch or Nijmegen." } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4229fedf62fd1b07.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4229fedf62fd1b07/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4229fedf62fd1b07?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.