# com.acuris-geo/acuris-mcp (remote · api.acuris-geo.com)

Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment

- Trust score: 62/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.acuris-geo.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-acuris-geo-acuris-mcp/api.md), [page](https://verifymcp.io/servers/com-acuris-geo-acuris-mcp/api)

## Channel facts

- Endpoint: `https://api.acuris-geo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1525 tokens (~190/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-acuris-geo-acuris-mcp https://api.acuris-geo.com/mcp
```

### Codex

```toml
[mcp_servers.com-acuris-geo-acuris-mcp]
url = "https://api.acuris-geo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-acuris-geo-acuris-mcp": {
      "type": "remote",
      "url": "https://api.acuris-geo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-acuris-geo-acuris-mcp --url https://api.acuris-geo.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-acuris-geo-acuris-mcp:
    url: "https://api.acuris-geo.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-acuris-geo-acuris-mcp": {
      "type": "http",
      "url": "https://api.acuris-geo.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 62, +1)

- [security] Tool “geocode_address” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 172 → 190

### 2026-08-01 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (8)

### `validate_address` (~265 tokens)

Validate and standardize one postal address (240+ countries; UK via the
    official Royal Mail PAF with UDPRN + UPRN).

    Give `country` as ISO-3 lowercase (e.g. usa, can, deu, gbr) plus EITHER a
    free-text `address_line` OR fielded parts (street, house_number, city,
    state, postcode). Returns an honest verdict — status "verified" (exact) or
    "corrected" (fixed), or partial_match with reasons — plus the standardized
    form, confidence, coordinates with an explicit accuracy_type, and, for
    street-accurate USA/Canada matches, a FREE `enrichment` block (census
    tract, block group, FIPS, CBSA/MSA, congressional district, school
    district / Canadian equivalents).

    Cost: 1 validation credit per successful lookup; no-match and errors are
    refunded automatically (you pay for results, not attempts).

Input parameters:

- `address_line` (string)
- `city` (string)
- `country` (string, required)
- `house_number` (string)
- `postcode` (string)
- `state` (string)
- `street` (string)

### `validate_addresses_batch` (~171 tokens)

Validate up to 50 addresses in one call (mixed countries allowed).

    `addresses` is a list where each entry is either a free-text string, or an
    object {"input": <string or fielded object>, "country": "iso3"}. Entries
    without their own country use the `country` parameter. UK (gbr) rows are
    routed individually to the Royal Mail PAF service; everything else goes
    through the batch endpoint. Results come back in the same order, each with
    the same shape as validate_address.

    Cost: 1 validation credit per successfully validated row; failed rows are
    refunded. For files bigger than 50 rows, call this tool repeatedly.

Input parameters:

- `addresses` (array, required)
- `country` (string)

### `enrich_us_ca_address` (~231 tokens)

Address → census & geographic codes (USA + Canada), FREE with validation.

    USA: state & county FIPS, census tract (11-digit GEOID), block group,
    CBSA/MSA, congressional district (119th Congress), school district.
    Canada: province, census division, dissemination area, census subdivision,
    census tract, CMA/CA, federal electoral district. Sources: US Census
    Bureau TIGER/Line; Statistics Canada (open data).

    The enrichment is attached when the address resolves to a house-number- or
    street-accurate match; centroid-only matches return no enrichment (the
    point could fall in the wrong area). `country` must be "usa" or "can".

    Cost: 1 validation credit (the enrichment itself is free); failed lookups
    are refunded.

Input parameters:

- `address_line` (string)
- `city` (string)
- `country` (string, required)
- `house_number` (string)
- `postcode` (string)
- `state` (string)
- `street` (string)

### `geocode_address` (~317 tokens)

Forward-geocode an address to coordinates (lat/lng) with an explicit
    accuracy_type — you always know what you got.

    accuracy_type is an OPEN set; new tiers are added as reference data
    improves. Do NOT write code that treats an unrecognised value as a failure.
    Branch on the boolean `point_coordinate` instead, which is true when the
    coordinate identifies one address. Current values: rooftop and
    arrival_point (both point coordinates — a point on the building, or the
    property's entrance / access point), then street_interpolated,
    street_centroid, postcode_centroid, locality_centroid, admin_centroid.

    House-number-level matches may ALSO carry `arrival_point: {lat, lng}` —
    the premise's entrance/access coordinate beside the served pin (equal to
    lat/lng when accuracy_type is arrival_point). Use it for delivery and
    navigation; omitted when not on file.

    `country` is ISO-3 lowercase. Give fielded parts or a single line in `q`.
    For UK (gbr) addresses use validate_address instead — it returns point
    coordinates from Royal Mail PAF.

    Cost: 1 credit per successful geocode; failures are refunded.

Input parameters:

- `city` (string)
- `country` (string, required)
- `house_number` (string)
- `postcode` (string)
- `q` (string)
- `state` (string)
- `street` (string)

### `reverse_geocode` (~115 tokens)

Coordinates → nearest address(es). Returns the closest reference
    addresses to (lat, lng), nearest first, with distances.

    Optional: `country` (ISO-3) to constrain the search, `radius_m`, `limit`.

    Cost: 1 credit per successful lookup; an empty radius (no addresses found)
    is refunded.

Input parameters:

- `country` (string)
- `lat` (number, required)
- `limit` (integer)
- `lng` (number, required)
- `radius_m` (integer)

### `expand_uk_postcode` (~88 tokens)

Expand a UK postcode into every Royal Mail delivery point at that
    postcode — organisation, building, street, town, county, plus UDPRN, UPRN
    and rooftop coordinates for each address.

    Cost: 1 credit per postcode, regardless of how many addresses come back;
    an unknown/invalid postcode is refunded automatically.

Input parameters:

- `postcode` (string, required)

### `check_balance` (~52 tokens)

Show the connected API key's remaining credit balances (validation,
    geocode, email, phone pools; trial expiry; the UK free-trial PAF counter
    for trial keys). Free — never consumes credits.

### `request_trial_key` (~146 tokens)

Get an instant FREE Acuris trial API key — 100 credits, valid 7 days,
    no card, no signup form. Idempotent: asking again with the same email
    within 24h returns the SAME key.

    After receiving the key, reconfigure this MCP server connection with the
    header "Authorization: Bearer <key>" (or set ACURIS_API_KEY for stdio).
    Trial limits: shared per-IP daily caps and a lifetime cap of 40 UK (Royal
    Mail PAF) lookups. Paid plans: https://www.acuris-geo.com/acuris-pricing/

Input parameters:

- `email` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-acuris-geo-acuris-mcp/api#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 61
- 2026-07-31: 60
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://api.acuris-geo.com/mcp
- Repository: https://github.com/Acuris-GmbH/acuris-mcp
- Website: https://api.acuris-geo.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-acuris-geo-acuris-mcp/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-acuris-geo-acuris-mcp/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-acuris-geo-acuris-mcp/api