Acuris MCP Server

Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment. The acuris mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

Give any AI agent — Claude, Cursor, ChatGPT, Gemini CLI and every other MCP-capable client — direct, self-describing access to Acuris address validation and geocoding: 240+ countries, honest verified / corrected / partial verdicts, UK addresses against the official Royal Mail PAF (UDPRN + UPRN), and free census & geographic enrichment for street-accurate USA/Canada matches (census tract, block group, FIPS, CBSA/MSA, congressional district, school district — Canadian equivalents included).

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• validate_address — Validate & standardize one address (240+ countries; UK via Royal Mail PAF with UDPRN + UPRN). Street-accurate USA/Canada matches include the free
• validate_addresses_batch — Up to 50 addresses per call, mixed countries. Results in input order
• enrich_us_ca_address — Address → census tract, block group, county/state FIPS, CBSA/MSA, congressional district, school district (USA) / dissemination area, census
• geocode_address — Forward geocoding with an explicit accuracy_type on every result
• reverse_geocode — Coordinates → nearest addresses with distances
• expand_uk_postcode — UK postcode → every Royal Mail delivery point (organisation, UDPRN, UPRN, rooftop coordinates)
• check_balance — Remaining credit balances for the connected key
• request_trial_key — Instant free trial key by email (idempotent for 24h)

Configuration

You will need 3 environment variables: ACURIS_API_KEY, YOUR_ACURIS_API_KEY, YOUR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the acuris mcp server does with a few real requests.

When to reach for it

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Acuris's toolset — validate_address, validate_addresses_batch, enrich_us_ca_address and 5 more — is a fair guide to whether it matches your workflow. It is maintained by com.acuris-geo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.