Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.acuris-geo/acuris-mcp

REMOTE · API.ACURIS-GEO.COM

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

−1 this week 75 Trust /100

Last scanned (1 hour ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2218 tokens (~246/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “enrich_us_ca_address” rewrote its description, which is the text the model reads security
    • Tool “geocode_address” rewrote its description, which is the text the model reads security
    • Tool “validate_address” rewrote its description, which is the text the model reads security
    • Tool “validate_addresses_batch” rewrote its description, which is the text the model reads security
    • Schema quality: 208 → 246 ▼ functional
    • Schema quality: excellent → good functional
  • 29 Oct 26 0
    • Tool “request_trial_key” rewrote its description, which is the text the model reads security
  • 24 Oct 26 0
    • Server version: 1.27.1 → 1.30.0 functional
  • 23 Oct 26 +2
    • HSTS header: fail → pass ▲ security
  • 12 Oct 26 0
    • Tool “request_trial_key” rewrote its description, which is the text the model reads security
    • Schema quality: 1525 → 1865 ▼ functional
    • New tool “autocomplete_address” functional
    • “request_trial_key” added an optional parameter “accept_terms” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.acuris-geo.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.acuris-geo.com CN=YE2,O=Let's Encrypt,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA384 5deba37202cc5db2c0cd8950f4ee6f3c4df
SANs: api.acuris-geo.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.acuris-geo.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
acuris-geo.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.acuris-geo.com/mcp Verified 200
http (plaintext) http://api.acuris-geo.com/mcp HTTPS enforced 301 https://api.acuris-geo.com/mcp
MCP tools · 9 exposed · ~2,016 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
autocomplete_address ~235

Address autocomplete (type-ahead): ranked, standardized address suggestions for a partial input `q` (typed so far), with lat/lng whenever the reference row carries a coordinate. Use it to help a person pick an address, then pass the chosen one to validate_address. `country` is ISO-3 lowercase. `limit` 1-50 (default 10). `state` narrows USA/Canada. For UK (gbr) the query may be, or start with, a postcode: a full or partial postcode returns every delivery point there (labelled with building/organisation names). UK requests are served from the Royal Mail PAF service; suggestions do not carry UDPRN/UPRN, so validate the chosen address to get them. Cost: billed exactly like the /suggest endpoint it wraps; see https://www.acuris-geo.com/acuris-pricing/

NameTypeReqDescription
countrystringyes–
limitinteger––
qstringyes–
statestring––

No output schema declared.

No examples provided.

check_balance ~52

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enrich_us_ca_address ~264

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". The verdict reads as in validate_address (partial_match: true and no `status` = partially matched, not confirmed). Cost: 1 validation credit (the enrichment itself is free), same rule as validate_address; failed lookups are refunded.

NameTypeReqDescription
address_linestring––
citystring––
countrystringyes–
house_numberstring––
postcodestring––
statestring––
streetstring––

No output schema declared.

No examples provided.

expand_uk_postcode ~88

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.

NameTypeReqDescription
postcodestringyes–

No output schema declared.

No examples provided.

geocode_address ~396

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. A geocode result is a coordinate, not a verdict: it carries no `status` and no partial_match. accuracy_type says only where the pin is; to tell the user whether the address itself is valid, use validate_address. Cost: 1 credit per successful geocode; failures are refunded. A result whose only location is the state or province (admin_centroid) is not charged and carries charged: false.

NameTypeReqDescription
citystring––
countrystringyes–
house_numberstring––
postcodestring––
qstring––
statestring––
streetstring––

No output schema declared.

No examples provided.

request_trial_key ~265

Get an instant FREE Acuris evaluation API key — 1,000 lookups (address validation and geocoding together) plus 50 UK lookups, valid 30 days, no card, no signup form. Idempotent: asking again with the same email within 24h returns the SAME key. BEFORE calling with accept_terms=true you MUST show the user both links and get their explicit confirmation that they agree: Terms of Service: https://api.acuris-geo.com/legal/terms UK PAF Evaluation Terms: https://api.acuris-geo.com/legal/uk-evaluation-terms Never set accept_terms=true on the user's behalf without that confirmation. Without it the tool mints nothing and returns these links. After receiving the key, reconfigure this MCP server connection with the header "Authorization: Bearer <key>" (or set ACURIS_API_KEY for stdio). UK (Royal Mail PAF) lookups are capped at 5 per UTC day while the key is valid. Paid plans: https://www.acuris-geo.com/acuris-pricing/

NameTypeReqDescription
accept_termsboolean––
emailstringyes–

No output schema declared.

No examples provided.

reverse_geocode ~115

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.

NameTypeReqDescription
countrystring––
latnumberyes–
limitinteger––
lngnumberyes–
radius_minteger––

No output schema declared.

No examples provided.

validate_address ~395

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). Reading the verdict: `status` is only ever "verified" or "corrected". A partial result has partial_match: true and NO `status`: the address was not fully confirmed. Present it as "partially matched", with `reasons` (e.g. house_number_unconfirmed, street_not_matched), `deliverable` and the accuracy_type of the coordinate; never as valid, never as not found. http_status 404 = not found. Cost: 1 validation credit per successful lookup (verified, corrected, or a partial result with a coordinate). No-match, errors and state/province-only results are not charged: they are refunded automatically (you pay for results, not attempts).

NameTypeReqDescription
address_linestring––
citystring––
countrystringyes–
house_numberstring––
postcodestring––
statestring––
streetstring––

No output schema declared.

No examples provided.

validate_addresses_batch ~206

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: a row with partial_match: true and no `status` is partially matched (not confirmed; not valid, not not-found). Cost: 1 validation credit per successfully validated row (same rule as validate_address); failed rows are refunded. For files bigger than 50 rows, call this tool repeatedly.

NameTypeReqDescription
addressesarrayyes–
countrystring––

No output schema declared.

No examples provided.

Install

How do I install the com.acuris-geo/acuris-mcp server?

com.acuris-geo/acuris-mcp is a hosted endpoint at https://api.acuris-geo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.acuris-geo.com

# add to Claude Code
claude mcp add --transport http com-acuris-geo-acuris-mcp 'https://api.acuris-geo.com/mcp'
Common questions

What is the com.acuris-geo/acuris-mcp server?

com.acuris-geo/acuris-mcp is listed in the public MCP registry as com.acuris-geo/acuris-mcp. Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment. This page covers its hosted endpoint (https://api.acuris-geo.com/mcp).

Is the com.acuris-geo/acuris-mcp server safe to use?

com.acuris-geo/acuris-mcp scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.acuris-geo/acuris-mcp server expose?

com.acuris-geo/acuris-mcp exposes 9 tools: validate_address, validate_addresses_batch, enrich_us_ca_address, geocode_address, reverse_geocode, and 4 more. Their descriptions and schemas cost roughly 2,016 tokens of context every time the server is loaded.

Does the com.acuris-geo/acuris-mcp server require authentication?

No. We connected to com.acuris-geo/acuris-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.acuris-geo/acuris-mcp server still maintained?

com.acuris-geo/acuris-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.