Skip to content
RightDoor
Sign inStart for free

AI agents · MCP server

Let your assistant check the address, not guess it.

Language models can sound sure about addresses that don't exist. Connect RightDoor and your assistant asks the official register instead, and tells you which one it asked.

Works with Claude and other MCP clients.

Connect your assistantStart free
Illustrative conversation. The tool's answer is the register's, captured from the RightDoor API on 11 October 2026. Address: the Dutch parliament.

Connect

Pick your client. Two minutes.

The server lives at https://api.rightdoor.eu/mcp (Streamable HTTP). Add it to your client, sign in with your RightDoor account when the client asks, and allow it. No account yet? Start free: 2,500 verifications a month, no card needed.

Claude

Add RightDoor to Claude

  1. In Claude (claude.ai or the desktop app), open Settings → Connectors → Add custom connector.
  2. Paste the server address.
  3. Sign in to RightDoor, check the app's name and the site it comes from, and allow it.
Server address
https://api.rightdoor.eu/mcp

Claude Code

Add RightDoor to Claude Code

  1. Run this in your terminal.
  2. Sign in to RightDoor when Claude Code asks, and allow it.
Terminal
claude mcp add --transport http rightdoor https://api.rightdoor.eu/mcp

Cursor

Add RightDoor to Cursor

  1. Add the server to ~/.cursor/mcp.json.
  2. Sign in to RightDoor when Cursor asks, and allow it.
mcp.json
{
  "mcpServers": {
    "rightdoor": { "url": "https://api.rightdoor.eu/mcp" }
  }
}

VS Code

Add RightDoor to VS Code

  1. Add the server to .vscode/mcp.json.
  2. Sign in to RightDoor when VS Code asks, and allow it.
mcp.json
{
  "servers": {
    "rightdoor": { "type": "http", "url": "https://api.rightdoor.eu/mcp" }
  }
}

Other MCP clients

Connect any MCP client

  1. Add the server address to your client's MCP configuration.
  2. Sign in to RightDoor when the client asks, and allow it.
  3. The five tools appear in your agent.

Any client that speaks MCP over Streamable HTTP works: the server follows spec revision 2026-07-28 and still answers clients of the 2025 revisions.

Server address
https://api.rightdoor.eu/mcp

Claude, Cursor and VS Code are named only as clients that can connect to RightDoor; RightDoor isn't affiliated with or endorsed by their makers.

What your agent can do

Five tools. All read-only.

Every tool looks things up and never changes anything.

verify_address

Checks one address, written on one line (names and commas are fine) or in parts, and returns it corrected and formatted.

Counts as: 1 verification

verify_addresses_batch

Checks up to 100 addresses with your own ids, for order lists; results come back in order.

Counts as: 1 per address

lookup_address

Lists every address at a postcode and house number, with the additions (toevoeging, bus) to choose from.

Counts as: 1 verification

suggest_address

Completes a partial address: up to 10 suggestions while the user types.

Counts as: 1 per 10 calls

list_supported_countries

Lists the countries, the inputs each needs and the register versions.

Counts as: free

Answers your agent can act on.

Each answer has structured content for the agent and a short summary for clients that read only text. It carries the address as ready-to-use postal lines, so agents never assemble one themselves, plus issue codes, the register it came from, and a nextStep the agent can act on:

An agent checks an order
→ verify_address { "country": "NL", "street": "binenhof", "houseNumber": "1a", "postcode": "2513aa", "city": "amsterdam", "lang": "en" }

← status: corrected (medium confidence)
  formatted: ["Binnenhof 1 A", "2513 AA 's-Gravenhage"]
  issues: STREET_MISMATCH, CITY_MISMATCH
  provenance: Kadaster BAG, nl-bag:2026-10-01+nl-lvbag:2026-10-08
  nextStep: "The address was corrected. Show the corrected address to the customer and use it if they agree."

The same check as the API's, captured 11 October 2026.

  • valid: use the formatted address.
  • corrected: show the corrected address and use it if the person agrees.
  • ambiguous: ask which one (an apartment, a box, or the country), then check again.
  • invalid: ask the person to check the part the issue names.

blocking is advice. RightDoor never refuses a real customer on its own, and new builds the register already knows count as valid. When RightDoor can't answer, the agent should accept the address as given and check it later. A whole address on one line works too; a name before the street is left out of the check and returned as recipient.

Sign in, or use a key

  • OAuth (recommended for assistants): the client opens RightDoor's sign-in page, you sign in (with your two-factor code if it's on) and allow the app. You see the app's name and the site it comes from before anything is shared. Disconnect it any time under Security → Connected apps in the dashboard.
  • API key (for agents on your own servers): send Authorization: Bearer rd_live_…. Create keys in the dashboard; test keys (rd_test_…) are free and limited to 100 calls a day.
Claude Code with an API key
claude mcp add --transport http rightdoor https://api.rightdoor.eu/mcp \
  --header "Authorization: Bearer rd_live_…"
mcp.json with an API key (Cursor)
{
  "mcpServers": {
    "rightdoor": {
      "url": "https://api.rightdoor.eu/mcp",
      "headers": { "Authorization": "Bearer rd_live_…" }
    }
  }
}

You stay in control

See every app. Disconnect any.

Sign in, don't paste keys

Assistants use your RightDoor sign-in. No secret key ends up in a chat.

One button per app

Security → Connected apps lists every assistant you allowed, the site it comes from and since when, with a Disconnect button.

See connected apps

Nothing kept

Addresses your agent sends are compared with the register in memory and forgotten. Hosted in Amsterdam.

Limits and pricing

  • The same plans as the API. A check through an agent counts like one through the API: one verification per address. The free plan includes 2,500 a month; see pricing.
  • Agent limits, on top of your plan's: 60 tool calls a minute (bursts of 20; a batch counts its addresses) and 10,000 a day per account.
  • No loops. The same request more than 5 times in a minute is refused, with a note telling the agent to stop retrying and ask the person.
  • Input: fields up to 200 characters, an address on one line up to 500, a batch up to 100 addresses.
  • No bulk lists. The tools answer about one address or one house number at a time; they never list a street, a postcode or a city.

Privacy

RightDoor keeps no addresses an agent sends: it compares them with the public registers in memory and forgets them. Logs hold the tool's name, the outcome, the time it took and your account id, never what was sent or answered. Everything runs in the EU (Amsterdam).

If your agent sends addresses of your customers, you are the controller and RightDoor the processor, under the data processing agreement. More in the privacy policy.

Agents that use REST

Agents that call HTTP APIs directly can read api.rightdoor.eu/llms.txt: the endpoints, every issue code and what to do about it, in one short text file. The REST answers carry the same nextStep and provenance as the tools; the full reference is at api.rightdoor.eu/docs (OpenAPI).

Building your own agent? Use the API.

The API