Koskamo

Koopscan MCP

An official MCP server operated by Koopscan that allows AI assistants to query Dutch address data. It provides building facts from the BAG register, registered energy labels, and human-reviewed crime signals for 77 Dutch cities. The server supports tools to resolve specific addresses and list news sources behind crime signals, facilitating real estate and safety research without requiring authentication.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

Koopscan MCP logo, by KoopscanNo sign-inEndpoint checked 2026-10-19Operated by Koopscan
MCP endpoint (Streamable HTTP)
https://mcp.koopscan.com/mcp
Vendor documentation

What you can do with it

  • Resolve a Dutch address to get building facts and energy labels
  • List news articles behind crime signals for a specific postcode
  • Check crime signal coverage and details for Dutch neighborhoods
Tools advertised by the last live check:
  • lookup_address
  • crime_sources

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http koopscan-mcp https://mcp.koopscan.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add koopscan-mcp --url https://mcp.koopscan.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable koopscan-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "koopscan-mcp": {
      "url": "https://mcp.koopscan.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "koopscan-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.koopscan.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start koopscan-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "koopscan-mcp": {
      "type": "http",
      "url": "https://mcp.koopscan.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http koopscan-mcp https://mcp.koopscan.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "koopscan-mcp": {
      "url": "https://mcp.koopscan.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "koopscan-mcp": {
      "serverUrl": "https://mcp.koopscan.com/mcp"
    }
  }
}

Ground your agent in cited data

Koopscan MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Do you run Koopscan MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing