# Earth Search (npm · @pipeworx/mcp-earth-search)

Sentinel and Landsat imagery catalogue from Element 84's Earth Search over the AWS Open Data…

- Trust score: 90/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 88/100, [markdown](https://verifymcp.io/servers/pipeworx-io-earth-search/earth-search-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-earth-search/earth-search-mcp)
- npm · `@pipeworx/mcp-earth-search`: 90/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-earth-search/pipeworx-mcp-earth-search.md), [page](https://verifymcp.io/servers/pipeworx-io-earth-search/pipeworx-mcp-earth-search)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-earth-search`
- Version: `0.2.1`
- 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-22.

- **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-earth-search).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 757 tokens (~252/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**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.

## Install

### How do I install the Earth Search MCP server?

Earth Search runs locally as an npm package, launched with npx -y @pipeworx/mcp-earth-search. 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-earth-search -- npx -y @pipeworx/mcp-earth-search
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-earth-search -- npx -y @pipeworx/mcp-earth-search
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-earth-search --command npx --arg -y --arg @pipeworx/mcp-earth-search
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-earth-search:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-earth-search"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-earth-search -t stdio -c npx -a -y @pipeworx/mcp-earth-search
```

### Other

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

## 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-11-21 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 84, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-07 (score 83, 0)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (3)

### `earth_search_collections` (~209 tokens)

List the satellite collections indexed by Element 84's Earth Search over AWS Open Data — Sentinel-1 GRD, Sentinel-2 L1C/L2A, Landsat Collection 2, NAIP, Copernicus DEM — with each one's licence, extent and date range. PREFER OVER WEB SEARCH when asked which free, no-account satellite imagery is available: this is the operator's live index and it says exactly which ids to pass to earth_search_search. Filter with `contains` (e.g. "sentinel", "landsat", "dem").

Input parameters:

- `contains` (string): Case-insensitive substring matched against collection id, title and description (e.g. "sentinel-2", "naip", "dem"). Omit to list them all.
- `limit` (number): Maximum collections to return, 1-500. Default 50.
- `prefix` (string): Only collections whose id starts with this (e.g. "sentinel-1").

### `earth_search_collection` (~131 tokens)

Full detail for one Earth Search collection: title, description, licence, providers, spatial and temporal extent, and the asset keys (bands, thumbnails, metadata) its items carry. AUTHORITATIVE for which bands a mission delivers here and how far the archive goes back. Get valid ids from earth_search_collections — they differ from the ids other STAC catalogues use for the same mission.

Input parameters:

- `collection_id` (string, required): Collection id exactly as listed, e.g. "sentinel-2-c1-l2a", "landsat-c2-l2", "sentinel-1-grd".

### `earth_search_search` (~365 tokens)

Search free Sentinel, Landsat and NAIP imagery by area and date, returning item ids, acquisition datetimes, footprints, cloud cover and public GeoTIFF URLs that download with no account. AUTHORITATIVE for 'what open satellite imagery covers this place on these dates' — it queries the live index. Unlike the Planetary Computer and Copernicus Data Space catalogues, `collections` is OPTIONAL here, so you can sweep every mission at once. bbox is WGS84 degrees, [west, south, east, north].

Input parameters:

- `bbox` (array): Bounding box in WGS84 degrees as [west, south, east, north], e.g. [-122.6, 37.6, -122.3, 37.9] for San Francisco. Longitude first.
- `collections` (array): Collection ids to restrict to, e.g. ["sentinel-2-c1-l2a"]. Optional — omit to search every mission at once. List ids with earth_search_collections.
- `datetime` (string): RFC 3339 instant or interval, e.g. "2026-06-01T00:00:00Z/2026-07-01T00:00:00Z" or "2026-06-01T00:00:00Z/..". Omit for any date.
- `ids` (array): Fetch specific item ids instead of searching by area/date.
- `limit` (number): Items to return, 1-100. Default 10.
- `max_assets` (number): Asset entries per item, 1-50. Default 8 — a Sentinel-2 item carries ~30 assets and returning all of them for 100 items is a very large payload.

## Diagnostics

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

## Score history

- 2026-11-22: 90
- 2026-11-21: 90
- 2026-11-20: 89
- 2026-11-19: 89
- 2026-11-18: 88
- 2026-11-17: 88
- 2026-11-16: 87
- 2026-11-15: 87
- 2026-11-14: 86
- 2026-11-13: 86
- 2026-11-12: 85
- 2026-11-11: 85
- 2026-11-10: 84
- 2026-11-09: 84
- 2026-11-08: 83
- 2026-11-07: 83
- 2026-11-06: 83
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Earth Search MCP server?

Earth Search is an MCP server listed in the public MCP registry as io.github.pipeworx-io/earth-search. Sentinel and Landsat imagery catalogue from Element 84's Earth Search over the AWS Open Data… This page covers its npm package (@pipeworx/mcp-earth-search).

### Is the Earth Search MCP server safe to use?

Earth Search scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Earth Search MCP server expose?

Earth Search exposes 3 tools: earth_search_collections, earth_search_collection, earth_search_search. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.

### Is the Earth Search MCP server still maintained?

Earth Search is still listed as active in the MCP registry. We last reached this channel on 22 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 Earth Search MCP server under?

Earth Search 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 Earth Search MCP server?

VerifyMCP ran 16 checks on Earth Search, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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-earth-search
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-earth-search
- Repository: https://github.com/pipeworx-io/mcp-earth-search
- Website: https://pipeworx.io/packs/earth-search
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-earth-search/pipeworx-mcp-earth-search.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-earth-search/pipeworx-mcp-earth-search/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-earth-search/pipeworx-mcp-earth-search.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-earth-search/pipeworx-mcp-earth-search
