@pipeworx/mcp-factline-nl

Dutch address, vehicle and school facts in English, from official Dutch registers, via Factline: any address (year built, floor area, use, neighbourhood figures, liveability), any licence plate (make, model, APK expiry, recalls, odometer verdict) and the nearest schools to a postcode.

Part of Pipeworx — an MCP gateway connecting AI agents to 1864+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• nl_address_facts(postcode, house_number, house_letter?, addition?) — building year and age, floor area, use, municipality and neighbourhood, residents, households, average home value, owner-occupied share, Leefbaarometer liveability percentile, energy label, municipality house-price trend.

• nl_vehicle_by_plate(licence_plate) — make, model, vehicle type, colour, first registration, fuel, euro class, APK expiry and validity, insured flag, open-recall flag, odometer verdict, risk level. Describes the vehicle only; no owner data.

• nl_schools_near_postcode(postcode) — nearest primary and secondary schools with pupils, denomination, distance and the latest test or exam results against the national figure.

Every answer carries source (publisher and dataset) and data_as_of. An address or plate that does not resolve returns found:false with the reason.

Related MCP server: mcp-overheid-nl

Auth

Keyless. The free basic reports need no key. If a Factline partner key is supplied (_apiKey, sent as x-api-key) the per-IP limit on these free reports is lifted. The paid Factline reports are not used by this pack.

Data sources

• Kadaster, Basisregistratie Adressen en Gebouwen (BAG) — addresses and buildings (public domain).

• Statistics Netherlands (CBS), neighbourhood key figures (CC BY 4.0).

• Ministry of the Interior and Kingdom Relations (BZK), Leefbaarometer (CC0).

• RVO, energy labels.

• RDW, vehicle register open data (CC0).

• DUO, school register and results.

Compiled and served in English by Factline (factline.dev), which also supplies the factline-x402-health pack.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "factline-nl": {
      "url": "https://gateway.pipeworx.io/factline-nl/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/factline-nl/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1864+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/nl_address_facts \
  -H 'Content-Type: application/json' \
  -d '{"postcode":"1012JS","house_number":1}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/nl_address_facts. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-factline-nl is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/factline-nl/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "factline-nl": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-factline-nl"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Factline Nl data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides

• pipeworx.io

License

MIT