com.acuris-geo/acuris-mcp
REMOTE · API.ACURIS-GEO.COM · SCANNED AUG 3
Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.acuris-geo.com
claude mcp add --transport http com-acuris-geo-acuris-mcp https://api.acuris-geo.com/mcp
[mcp_servers.com-acuris-geo-acuris-mcp] url = "https://api.acuris-geo.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-acuris-geo-acuris-mcp": {
"type": "remote",
"url": "https://api.acuris-geo.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-acuris-geo-acuris-mcp --url https://api.acuris-geo.com/mcp --transport streamable-http
mcp_servers:
com-acuris-geo-acuris-mcp:
url: "https://api.acuris-geo.com/mcp" {
"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.
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.
- 3 Aug 26 +1
- Tool “geocode_address” rewrote its description, which is the text the model reads security
- Schema quality: 172 → 190 ▼ functional
- 1 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 56
First indexed and scored.
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 3 Aug 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=YE1,O=Let's Encrypt,C=US | 14 Jun 2026 | 12 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 6fedec85e4fa8bc2f31565623dc898ddce3 |
| SANs: api.acuris-geo.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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 |
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 |
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.
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 ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address_line | string | — | — |
| city | string | — | — |
| country | string | yes | — |
| house_number | string | — | — |
| postcode | string | — | — |
| state | string | — | — |
| street | string | — | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | — |
No output schema declared.
No examples provided.
geocode_address ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | — |
| country | string | yes | — |
| house_number | string | — | — |
| postcode | string | — | — |
| q | string | — | — |
| state | string | — | — |
| street | string | — | — |
No output schema declared.
No examples provided.
request_trial_key ~146
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/
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | — |
| lat | number | yes | — |
| limit | integer | — | — |
| lng | number | yes | — |
| radius_m | integer | — | — |
No output schema declared.
No examples provided.
validate_address ~265
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address_line | string | — | — |
| city | string | — | — |
| country | string | yes | — |
| house_number | string | — | — |
| postcode | string | — | — |
| state | string | — | — |
| street | string | — | — |
No output schema declared.
No examples provided.
validate_addresses_batch ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | — |
| country | string | — | — |
No output schema declared.
No examples provided.