# Usgs National Map (npm · @pipeworx/mcp-usgs-national-map)

USGS The National Map (TNM) Access API MCP

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-usgs-national-map/usgs-national-map-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-usgs-national-map/usgs-national-map-mcp)
- npm · `@pipeworx/mcp-usgs-national-map`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map.md), [page](https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-usgs-national-map`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-usgs-national-map).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-usgs-national-map -- npx -y @pipeworx/mcp-usgs-national-map
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-usgs-national-map": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-national-map"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-usgs-national-map": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-national-map"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-usgs-national-map -- npx -y @pipeworx/mcp-usgs-national-map
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-usgs-national-map": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-usgs-national-map"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-usgs-national-map --command npx --arg -y --arg @pipeworx/mcp-usgs-national-map
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-usgs-national-map:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-usgs-national-map"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-usgs-national-map": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-usgs-national-map"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-usgs-national-map -t stdio -c npx -a -y @pipeworx/mcp-usgs-national-map
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-usgs-national-map": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-national-map"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `tnm_datasets` (~129 tokens)

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.

Input parameters:

- `filter` (string): Case-insensitive substring to narrow the catalog, e.g. "elevation", "lidar", "hydrography"

### `tnm_search_products` (~362 tokens)

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>".

Input parameters:

- `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)

### `tnm_products_at_point` (~189 tokens)

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.

Input parameters:

- `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, required): Latitude in WGS84 decimal degrees
- `limit` (number): Products to return, 1-100 (default 20)
- `longitude` (number, required): Longitude in WGS84 decimal degrees (negative in the US)
- `prod_formats` (string): Optional product format filter, e.g. "GeoTIFF"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-usgs-national-map
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-usgs-national-map
- Repository: https://github.com/pipeworx-io/mcp-usgs-national-map
- Website: https://pipeworx.io/packs/usgs-national-map
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-usgs-national-map/pipeworx-mcp-usgs-national-map