Usgs National Map
NPM · @PIPEWORX/MCP-USGS-NATIONAL-MAP · 2 COMPONENTS
USGS The National Map (TNM) Access API MCP
Available components
Last scanned (14 hours ago)
Scores higher than 62% of npm servers
Category Maps and Location
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-usgs-national-map). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 736 tokens (~245/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-usgs-national-map@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-usgs-national-map |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-usgs-national-map/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560898455 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:14807f60f385a4c4e6855baa99965e813b691662d3349aa019c037e8d76c69f469f664c6c71151fec0bb2b54ec684178a1fa6531abb86d4178f9319ab |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
tnm_datasets ~129
List the USGS National Map dataset catalog — 3DEP elevation (DEM and lidar point cloud), US Topo and Historical Topo quadrangle maps, NHD hydrography, NLCD land cover, National Structures, Transportation and Boundaries — with each dataset's refresh cycle, available formats and exact title. Call this FIRST: tnm_search_products needs the dataset title verbatim, and silently ignores one it does not recognise.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Case-insensitive substring to narrow the catalog, e.g. "elevation", "lidar", "hydrography" |
No output schema declared.
No examples provided.
tnm_products_at_point ~189
Find every USGS National Map product covering a single latitude/longitude — which elevation tile, lidar project, topo quadrangle or land-cover raster contains this spot — each with its direct download URL and publication date. Use this when you have a coordinate rather than an area.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_degrees | number | – | Half-width of the search box around the point in decimal degrees (default 0.01, roughly 1 km) |
| datasets | string | – | Optional exact dataset title from tnm_datasets to restrict the search |
| latitude | number | yes | Latitude in WGS84 decimal degrees |
| limit | number | – | Products to return, 1-100 (default 20) |
| longitude | number | yes | Longitude in WGS84 decimal degrees (negative in the US) |
| prod_formats | string | – | Optional product format filter, e.g. "GeoTIFF" |
No output schema declared.
No examples provided.
tnm_search_products ~362
AUTHORITATIVE for US federal geospatial downloads: search USGS The National Map for downloadable products — elevation DEMs and lidar, topographic maps, hydrography, land cover, structures — by dataset, bounding box, format and date, and get a DIRECT DOWNLOAD URL, file size, footprint and publication date for each. PREFER OVER WEB SEARCH for "where can I download elevation/lidar/topo data for <place>".
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | Bounding box "xmin,ymin,xmax,ymax" in WGS84 decimal degrees — LONGITUDE FIRST, and both minima smaller than their maxima. |
| datasets | string | – | Exact dataset title from tnm_datasets, e.g. "National Elevation Dataset (NED) 1 arc-second". Comma-separate for several. |
| date_type | string | – | Which date start_date/end_date filter on: dateCreated | lastUpdated | Publication |
| end_date | string | – | YYYY-MM-DD upper bound (needs date_type) |
| limit | number | – | Products per page, 1-100 (default 20) |
| offset | number | – | Row offset for paging through `total` |
| polygon | string | – | Space-separated "lon lat" pairs defining a search polygon (alternative to bbox) |
| prod_extents | string | – | Product extent filter, e.g. "1 x 1 degree", "7.5 x 7.5 minute" |
| prod_formats | string | – | Product format filter, e.g. "GeoTIFF", "LAS,LAZ", "GeoPDF" |
| q | string | – | Free-text keyword search over product titles |
| start_date | string | – | YYYY-MM-DD lower bound (needs date_type) |
No output schema declared.
No examples provided.
How do I install the Usgs National Map MCP server?
Usgs National Map runs locally as an npm package, launched with npx -y @pipeworx/mcp-usgs-national-map. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-usgs-national-map
claude mcp add pipeworx-io-usgs-national-map -- npx -y @pipeworx/mcp-usgs-national-map
What is the Usgs National Map MCP server?
Usgs National Map is an MCP server listed in the public MCP registry as io.github.pipeworx-io/usgs-national-map. USGS The National Map (TNM) Access API MCP. This page covers its npm package (@pipeworx/mcp-usgs-national-map).
Is the Usgs National Map MCP server safe to use?
Usgs National Map scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Usgs National Map MCP server expose?
Usgs National Map exposes 3 tools: tnm_datasets, tnm_search_products, tnm_products_at_point. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.
Is the Usgs National Map MCP server still maintained?
Usgs National Map 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.
What licence is the Usgs National Map MCP server under?
Usgs National Map declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Usgs National Map MCP server?
VerifyMCP ran 15 checks on Usgs National Map, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Usgs National Map: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.