AtlasFetch
NPM · ATLASFETCH-MCP · SCANNED SEP 21
Reverse geocode a coordinate to country, region and municipality, and match your own geofences.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1170 tokens (~292/item across 4 items; 4 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the AtlasFetch MCP server?
AtlasFetch runs locally as an npm package, launched with npx -y atlasfetch-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · atlasfetch-mcp
claude mcp add xyz-atlasfetch-atlasfetch -- npx -y atlasfetch-mcp
{
"mcpServers": {
"xyz-atlasfetch-atlasfetch": {
"command": "npx",
"args": [
"-y",
"atlasfetch-mcp"
]
}
}
} {
"servers": {
"xyz-atlasfetch-atlasfetch": {
"command": "npx",
"args": [
"-y",
"atlasfetch-mcp"
]
}
}
} codex mcp add xyz-atlasfetch-atlasfetch -- npx -y atlasfetch-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-atlasfetch-atlasfetch": {
"type": "local",
"command": [
"npx",
"-y",
"atlasfetch-mcp"
],
"enabled": true
}
}
} openclaw mcp add xyz-atlasfetch-atlasfetch --command npx --arg -y --arg atlasfetch-mcp
mcp_servers:
xyz-atlasfetch-atlasfetch:
command: "npx"
args: ["-y", "atlasfetch-mcp"] {
"McpServers": {
"xyz-atlasfetch-atlasfetch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"atlasfetch-mcp"
]
}
}
} assistant mcp add xyz-atlasfetch-atlasfetch -t stdio -c npx -a -y atlasfetch-mcp
{
"mcpServers": {
"xyz-atlasfetch-atlasfetch": {
"command": "npx",
"args": [
"-y",
"atlasfetch-mcp"
]
}
}
} 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.
- 20 Sept 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.
- 18 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 17 Sept 26 +9
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Source repository: fail → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 198 → 292 ▼ functional
- Security disclosure: unverified → fail ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.4 functional
- Package version: 0.1.1 → 0.1.3 functional
- Package version: 0.1.1 → 0.1.2 functional
- 16 Sept 26 49
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 21 Sept 2026 · Analysed npm/atlasfetch-mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_boundary Add a polygon to a boundary set ~493
Adds ONE polygon to an existing boundary set on this account, so that lookup_location reports when a point falls inside it — delivery zones, service areas, sales territories. Each call creates a new boundary: calling twice with the same name stores two. Before calling: the set must already exist (create_boundary_set). A set matches nothing in lookups until it is switched on and granted to an API key in the dashboard at https://atlasfetch.xyz/dashboard, which this server cannot do. geometry must be a single GeoJSON Polygon — not a MultiPolygon, Feature or FeatureCollection. Positions are [longitude, latitude]. Each ring needs at least 4 positions and must be closed (last position equals the first); extra rings are holes. Self-intersecting shapes are rejected. To store a MultiPolygon, add each part separately. Plan limits cap vertices per polygon (every position counts, including the closing one), properties per boundary and boundaries per set; a limit hit is refused with a message naming it. WITHOUT YOUR OWN KEY, the shared demo key is on the Public plan: at most 5 positions per polygon (a closed quadrilateral), properties only category (zone, area, route, place, other), color (green, blue, red, yellow, purple, orange) and priority (low, medium, high), and one set shared with every demo user, where adding to a full set silently deletes its oldest boundary. Never upload anything private with the demo key. Returns the stored boundary: id, set, name, properties, pointCount and createdAt.
| Name | Type | Req | Description |
|---|---|---|---|
| geometry | object | yes | A GeoJSON Polygon, e.g. {"type":"Polygon","coordinates":[[[18.40,-33.93],[18.40,-33.90],[18.44,-33.90],[18.44,-33.93],[18.40,-33.93]]]}. |
| name | string | yes | Label returned when a looked-up point falls inside this polygon, e.g. "Zone A". |
| properties | object | – | Optional flat key/value pairs returned with every match: keys up to 32 characters, values a string (up to 256 characters), number or boolean. The demo key accepts only category, color and priority, f… |
| set | string | yes | Name of an existing set on this account (see list_boundary_sets). |
No output schema declared.
No examples provided.
create_boundary_set Create a boundary set ~165
Creates an empty named set to hold your own polygons: delivery zones, service areas, sales territories. IMPORTANT, and not a bug: a new set is created unavailable and granted to no key, so it matches nothing until both are changed. Granting is addressed by API key id, and the only endpoint that lists key ids needs a browser session — which this server does not have. So this tool can create the set and add boundaries to it, but CANNOT make it queryable. Tell the user to finish that at https://atlasfetch.xyz/dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A short name, used to reference the set in lookups: 1-32 letters, digits, hyphens or underscores, starting with a letter or digit. |
No output schema declared.
No examples provided.
list_boundary_sets List the boundary sets on this account ~54
Lists the boundary sets on this account with their boundary counts and the API keys (id and label) each is granted to. A set only matches during a lookup when it is available AND granted to the key making the call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_location Look up the boundaries containing a coordinate ~398
Reverse geocode a coordinate to the administrative areas that contain it — country, region (state or province) and municipality — as names plus ISO 3166 codes, and match it against boundary sets the account has uploaded, in the same call. Use for: which country, region or municipality a point is in; geofence checks against your own polygons; tagging data with region codes. Do NOT use for: street addresses or postcodes (this is not forward geocoding, and results stop at the municipality), routing, distances, or fetching boundary geometry. Caveats worth repeating to the user: municipal is the finest unit AVAILABLE, not a consistent kind of thing — Los Angeles returns a city, rural Kansas returns a county, so do not assume it names a city. A layer that matched nothing comes back null. The errors array is always present: a boundary set that is unavailable or not granted to this key is skipped and reported there, while the call itself still succeeds. One call is one billed lookup however many layers, sets or grid codes it touches, and a call that matches nothing still bills.
| Name | Type | Req | Description |
|---|---|---|---|
| base | array | – | Which reference layers to resolve. Defaults to all three. |
| encode | array | – | Also return the point as an H3 cell index and/or Google Plus Code. Output only — neither can be used AS a location, because both name areas rather than points. |
| h3res | integer | – | H3 resolution 0-15. 9 is about 400 m across. |
| lat | number | yes | Latitude, -90 to 90. |
| lng | number | yes | Longitude, -180 to 180. |
| pluslen | – | – | Plus Code length. 9 is not a valid length. 10 is about 14 m. |
| sets | array | – | Names of the boundary sets on this account to match against. Defaults to none. |
No output schema declared.
No examples provided.
What is the AtlasFetch MCP server?
AtlasFetch is an MCP server listed in the public MCP registry as xyz.atlasfetch/atlasfetch. Reverse geocode a coordinate to country, region and municipality, and match your own geofences. This page covers its npm package (atlasfetch-mcp).
Is the AtlasFetch MCP server safe to use?
AtlasFetch scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 AtlasFetch MCP server expose?
AtlasFetch exposes 4 tools: lookup_location, list_boundary_sets, create_boundary_set, add_boundary. Their descriptions and schemas cost roughly 1,110 tokens of context every time the server is loaded.
Is the AtlasFetch MCP server still maintained?
AtlasFetch is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AtlasFetch MCP server under?
AtlasFetch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.