Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Earth Search

NPM · @PIPEWORX/MCP-EARTH-SEARCH · 2 COMPONENTS

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

+3 this week 90 Trust /100

Last scanned (1 hour ago)

Scores higher than 85% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

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-earth-search). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 21 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 7 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-earth-search@0.2.1

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-earth-search
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-earth-search/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3617576550
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0b8c289bddc6dc69e1493c9ad9c8877dcbc171ec82c1a2c15cfeba271e3a5a893499306f49f8a03dce77ca5a82e7045f3f30cb16697eddd4417a0d1cb

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~705 tokens

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 →

Tool Tokens
earth_search_collection ~131

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.

NameTypeReqDescription
collection_idstringyesCollection id exactly as listed, e.g. "sentinel-2-c1-l2a", "landsat-c2-l2", "sentinel-1-grd".

No output schema declared.

No examples provided.

earth_search_collections ~209

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

NameTypeReqDescription
containsstring–Case-insensitive substring matched against collection id, title and description (e.g. "sentinel-2", "naip", "dem"). Omit to list them all.
limitnumber–Maximum collections to return, 1-500. Default 50.
prefixstring–Only collections whose id starts with this (e.g. "sentinel-1").

No output schema declared.

No examples provided.

earth_search_search ~365

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

NameTypeReqDescription
bboxarray–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.
collectionsarray–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.
datetimestring–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.
idsarray–Fetch specific item ids instead of searching by area/date.
limitnumber–Items to return, 1-100. Default 10.
max_assetsnumber–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.

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-earth-search

# add to Claude Code
claude mcp add pipeworx-io-earth-search -- npx -y @pipeworx/mcp-earth-search
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.