acuris-mcp@1.1.1
VERIFIED· not startedPublisher claims: "MCP server for Acuris address validation, autocomplete & geocoding — 240+ countries, Royal Mail PAF (UK), free US/Canada census enrichment. Runs against your own Acuris API key." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
ACURIS_API_KEYConfiguration, not credentials: ACURIS_MCP_HOST, ACURIS_MCP_MAIN_BASE, ACURIS_MCP_PAF_BASE, ACURIS_MCP_PORT, ACURIS_MCP_TIMEOUT_S- Where it talks to
- acuris-geo.com (its own)
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for ACURIS_API_KEY and talks to acuris-geo.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.1.0
vet-skills diff acuris-mcp 1.1.0 1.1.1This version reaches for something 1.1.0 did not: 1 new host (acuris-geo.com) · 1 new credential variable (ACURIS_API_KEY). Compared from the two recorded runs, not from source.
- New hosts
- acuris-geo.com
- New credential variables
- ACURIS_API_KEY
1.1.0 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-22 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 838 lines in 6 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.