Mmcp.market

Is NASA Earthdata MCP server safe?

Probably. Read the findings first.

C64/100grade C

Use with care. Some checks failed or could not be verified.

Public scan report

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

2 low
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 622ms20/20
  • Tool poisoning7 tool descriptions checked13/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (2)

  • lowUnusually long tool description (over 2,000 characters)poison.long-description
    tool get_collections: …Search NASA CMR collections and return up to 10 lightweight normalized results. Key return fields in each item: - concept_id: CMR collection concept ID - native_id: native ID of the collection record - revision_id: revision ID of the collection metadata - provider_id: provider ID of the collection - short_name: collection short name - entry_title: collection title - time_start / time_end: temporal coverage bounds - processing_level_id: processing level (e.g., L3, L4) - doi: digital object identifier - collection_data_type: data type (e.g., SCIENCE_QUALITY, NEAR_REAL_TIME) - temporal_resolution / spatial_resolution: extracted resolution strings - related_urls: links to landing pages, documentation, and tools Unfiltered searches are supported when you need broad exploration. IMPORTANT — relevance and coverage: A keyword-only search returns all collections whose metadata mentions those terms, regardless of whether they actually hold data for the user's region or time period. Collection declared extents are often global or multi-decadal, so a collection appearing in results does not mean it has granules for a specific area or date. When the user's question involves a time period or geographic region, include temporal_start_date/temporal_end_date and/or spatial_wkt_geometry to restrict results to collections that overlap that window. Follow up with get_granules (with the same filters) to confirm actual data availability. IMPORTANT — keyword AND logic: CMR treats each space-separated keyword as an independent term and requires ALL of them to appear somewhere in a collection's metadata (title, summary, science keywords, instruments, platforms, etc.). Words do not need to appear in the same field or adjacent to each other. Because every term must match, adding more words makes the search STRICTER, not broader — the opposite of typical web search engines. Prefer 2–4 precise scientific terms. If a search returns 0 results, try removing the least essential word before broadening other filters. Phrase search (exact word sequence) is available by wrapping the value in escaped double quotes, but you cannot mix a phrase with additional standalone keywords. Key parameters: - keyword: free-text keyword search over collection metadata (AND logic; see above) - concept_id: exact collection concept ID - short_name: collection short name - provider: data provider short name - temporal_start_date / temporal_end_date: restrict to collections whose declared range overlaps this window; set when the user specifies a time period - spatial_wkt_geometry: restrict to collections whose declared extent intersects this area; set when the user specifies a geographic region Iteration & Refinement: - Results are strictly capped at 10 items to optimize context window usage. - If total_hits exceeds 10 and you lack the necessary results, do not attempt to page. Refine your search by adding tighter spatial, temporal, or keyword constraints. Tips: - Use scientific terms (variables, instruments, platforms) for better keyword relevance - Keep keyword queries to 2–4 precise terms; more words = stricter filter - If 0 results, drop the least essential keyword and retry before broadening other filters - Combine keyword + temporal + spatial filters for highest precision - Use short_name when you already know the target product…
  • lowNo source repository listedmaint.no-repo
Overall 64/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

NASA Earthdata MCP reviews, tools and install