Skip to main content
Glama
685,525 tools. Updated 2026-10-22 12:20

"Satellite" matching MCP tools:

  • Satellite image of any place on any date from NASA (daily true-color MODIS or VIIRS, or night lights), centered on a place or coordinates with your choice of area size. Good for storms, smoke, fires, snow and floods. Costs $0.005 USDC per call (x402).
    ConnectorNo auth
  • Satellite image of any place on any date from NASA (daily true-color MODIS or VIIRS, or night lights), centered on a place or coordinates with your choice of area size. Good for storms, smoke, fires, snow and floods. Costs $0.005 USDC per call (x402).
    ConnectorNo auth
  • Query the verified FCC satellite licensing docket — every space-station (SAT) filing in the FCC's own daily IBFS database dump, back to the 1960s — by applicant, application type, status, and filing date. Use this for "who is authorized to operate what in orbit, what has been filed, and where does each filing stand" questions — the satellite-buildout licensing pipeline. Each filing carries the FCC's public filing key (`file_number`, e.g. "SATLOA2025061800149"), the `callsign` (e.g. "S3069" = SpaceX Gen2), the application type and status in the FCC's OWN vocabulary — verbatim codes plus the FCC's own decode text from the same dump vintage (`app_type_code` "LOA" = Launch and Operating Authority, "STA" = Special Temporary Authority, "MOD" = Modification; `status_code` "A/C" = Action Complete, "ATPN" = Action Taken Public Notice — codebooks in describe) — the full lifecycle date family (filed / granted / expires / …), the FCC's plain-English `description` of the filing, and the applicant identity (`applicant_name`, the FCC's verbatim registrant, e.g. "Space Exploration Holdings, LLC"). Filter by `applicant_name`, `app_type_code`, `status_code`, `callsign`, `file_number`, `state` (the APPLICANT's address state), `applicant_country`, `report_period` (the filing date) via `report_period_from`/`report_period_to`, or `date_grant`/`date_expire` ranges. Group by any of `applicant_name`, `app_type_code`, `status_code`, `state`, `applicant_country`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"applicant_name": "Space Exploration Holdings, LLC", "group_by": ["app_type_code"]}` for one operator's filing mix; `{"report_period_from": "2020-01-01", "group_by": ["applicant_name"], "order_by": "source_record_count", "top_n": 10}` for the most active filers of the 2020s. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every record cites its exact row in the FCC's dump, re-verifiable via get_source_evidence_v1. THE ENGRAVED BOUNDARY: new-filing intake into IBFS structurally ENDED at the FCC's ICFS system cutover (~mid-2025), and ICFS publishes no bulk data — so filings SUBMITTED after the cutover are not in this docket, and counts near/after 2025 UNDERCOUNT new filing activity (say so when answering; every response carries an icfs_cutover note). The FCC has not regenerated this dump since 2026-07-16 (it previously updated daily), so status changes after that date are not reflected. For filings and actions since the cutover, use query_space_satellite_notices_v1 (the FCC's weekly satellite public notices). A filing is an authorization EVENT: never a satellite count (one NGSO grant can cover thousands of satellites), never an orbital catalog (satellites in orbit are not served here), never launch activity (FAA data, not served here). `state`/`applicant_city` are the APPLICANT's mailing address — satellites are not in states. Earth stations (SES) and non-satellite FCC dockets are out of scope. The one measure is `source_record_count` (filings in scope).
    ConnectorNo auth
  • Query the FCC Space Bureau's weekly satellite public notices since the ICFS cutover (2025-06-18) — every satellite application the FCC accepted for filing and every action it took (grants, partial grants, dismissals, surrenders), as printed. Use this for "what satellite filings has the FCC received or acted on since mid-2025" questions — the current licensing pipeline, which the pre-cutover docket (query_space_satellite_filings_v1) does not carry. Each record is one listing of a filing in one notice: the notice (`report_number` e.g. "SAT-02040", `notice_kind` "Applications Accepted for Filing" or "Actions Taken", `release_date`), the FCC `file_number` (e.g. "SAT-MOD-20260603-00225") and its `filing_type_code` (LOA, MOD, STA, AMD, T/C…), the `call_sign`, the `applicant` as printed (e.g. "Space Exploration Holdings, LLC"), the printed `date_filed` and `filing_type`, on Actions Taken notices the `action` (e.g. "Grant of Authority") and `action_date`, and the entry's full text as printed (`entry_text`, which carries the FCC's description of the request). Filter by `notice_kind`, `filing_type_code`, `action`, `applicant`, `report_number`, `file_number`, `call_sign`, `informative`, or the ranges `report_period_from`/`report_period_to` (release date), `date_filed_from`/`date_filed_to`, `action_date_from`/`action_date_to`. Group by `notice_kind`, `filing_type_code`, `action`, `applicant` or `report_number`. Pass each parameter as a top-level key of `params`. Example: `{"applicant": "Space Exploration Holdings, LLC", "include_records": true}` for SpaceX's listings; `{"notice_kind": "Actions Taken", "action": "Grant of Authority", "group_by": ["applicant"], "order_by": "source_record_count", "top_n": 10}` for the operators granted most often. Every record cites its line in the FCC's notice text, re-verifiable via get_source_evidence_v1. Read carefully: one filing can be listed in several notices, so `source_record_count` counts listings, not distinct filings. Values are what each notice prints: the same filing can show a different `date_filed` or applicant name in different notices. `action_date` is null when the notice prints none (the notice states its release date is then the effective date). The notices carry no status history and omit filings the FCC has not listed; a filing is never a satellite count, an orbital catalog or launch activity. Earth-station (SES) notices are out of scope.
    ConnectorNo auth
  • Check up to six production plots for forest loss after 31 December 2020, the cut-off in Regulation (EU) 2023/1115. Takes GeoJSON boundaries, the commodity, and the country of production. Returns a per-plot verdict, the loss years observed, how much of each plot was inspected, and a handle for the underlying satellite evidence. This answers Article 3(a) only: it does not check land tenure, permits, consent, or chain of custody, and it lists those gaps on every response. This has side effects, though it writes nothing to the organisation's records and costs no credits: every call asks emem.dev to make freshly signed measurements, so repeating a check returns the same finding under new signatures, and mints a short-lived evidence handle held on this server for 24 hours, which eudr_fetch_evidence resolves and which a later check will not reproduce.
    ConnectorNo auth
  • Get satellite-derived indicators aggregated over a country, one state/province, or a bounding box. Use for fires, emissions-based activity, rainfall, vegetation, temperature, and soil-moisture questions. For a sub-national area, call one state/province at a time. Informal regions such as "north India" or "the Midwest" have no boundary, so cover them with one call per state or a bounding box; using the whole country answers a different question. Grid cells and fire detections are activity snapshots, never fire perimeters. For ndvi_s2 and *_tropomi grids, drop or flag cells with low valid_obs_share. Results include units, source attribution, and caveats; cite the attribution. External-provider calls can take about 30 seconds, and rainfall or grid calls can take longer.
    ConnectorAPI key

Matching MCP Servers

  • A
    license
    B
    quality
    C
    maintenance
    Full-spectrum GEOINT server with 171 tools covering satellite imagery, aircraft tracking, maritime surveillance, military intelligence, conflict monitoring, environmental analysis, critical infrastructure, sanctions compliance, and cyber-geo intelligence from open-source data.
    100
    152 npm
    9
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Finds the clearest Sentinel-2, Landsat, Sentinel-1, or NAIP scene for any location and time, ranked by area coverage, cloud cover, and date, with previews and band download links.
    2
    1
    MIT

Matching MCP Connectors

  • Measure property from satellite imagery, price 24 trades, and install contractor quote widgets.

  • Aviation and space data: METAR/TAF, airports, space weather, aurora, asteroids, satellite passes.

  • Daily true-color satellite image of any area from NASA GIBS (MODIS Terra/Aqua or VIIRS, about 250 m per pixel, coastlines overlaid) as base64 JPEG. Useful to see clouds, smoke, snow, floods or fires on a given day. Params: place ("Zurich, Switzerland") or bbox [min_lat, min_lon, max_lat, max_lon] or lat + lon + radius_km (5 to 500, default 50), date (YYYY-MM-DD, default yesterday), layer (modis_terra default, modis_aqua, viirs_snpp, viirs_noaa20), width (64 to 1024, default 512), height (default from aspect). Price: $0.013 USDC per call, paid inside this MCP call via x402 (USDC on Base, Solana, Polygon or Arbitrum). x402 MCP clients such as @x402/mcp pay automatically. Free sample: call with the example input {"lat":47.37,"lon":8.54,"radius_km":60,"width":512}.
    ConnectorOAuth
  • Update the padlet's map style. - Purpose: Change the theme of a map padlet. - What this tool returns: { success: true } on successful update; otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }. Guidance for use: - You MUST ONLY use this tool in padlets in the "map" format. - Use this tool when the user requests to change the map style specifically, or the wallpaper/background of a "map" padlet. - You MUST ALWAYS return a different map style than the current one. - Besides updating the theme, you MUST also guide the user on how to choose a different one. - After calling this tool, you MUST include the map style widget in your response using this exact format: <pdlt-widget data-type="padlet_map_style" /> - Example response: "You can update the map styles through the "Settings" panel. <pdlt-widget data-type="padlet_map_style" />" - This is the list of supported themes: - Id: 100, Name: The Usual, Color scheme: light - Id: 101, Name: Silver, Color scheme: light - Id: 102, Name: Black Metal, Color scheme: dark - Id: 103, Name: Medieval, Color scheme: light - Id: 104, Name: Retro, Color scheme: light - Id: 105, Name: Tron, Color scheme: dark - Id: 106, Name: Night, Color scheme: dark - Id: 107, Name: Amusement Park, Color scheme: light - Id: 108, Name: Video Game, Color scheme: light - Id: 109, Name: Satellite, Color scheme: light - Id: 110, Name: Watercolor, Color scheme: light
    ConnectorOAuth
  • Find Criora's documents on a subject, to read and cite with fetch: a country's climate and disaster risk profile, a place's risk report, the pages on Criora's methodology and data sources, and the data catalogue (every climate layer with satellite data such as NDVI, and the country indicators). Each result has the id fetch reads and the Criora page to cite. Use it to find what Criora has before reading it with fetch. For an answer in one call the specific tools are shorter: assess_place for a place, get_country_profile for a country, rank_countries for the countries most at risk. A country is found by its ISO 3166-1 alpha-3 or alpha-2 code or its English name. The words methodology or sources find those pages; layers, catalogue, satellite, NDVI or indicators find the data catalogue. Only when nothing else matches is the query looked up as a place name, in the geocoder every user shares; a place is found best by its name alone. Nothing found is an empty list.
    ConnectorNo auth
  • Returns a 0-100 space-weather event index (severity-weighted counts of significant CMEs, M/X-class flares, and geomagnetic storms from NASA DONKI, trailing 14 days calibrated to a typical fortnight) with activity_index, per-type event counts, and recent_events (latest 8). Call when the user asks how eventful space weather has been recently or how many flares, CMEs, or storms occurred, or when timing satellite maneuvers, HF communications, or GNSS-precision fieldwork. Updates: daily.
    ConnectorNo auth
  • Fire clusters detected by satellite over the last N hours (default 24), worldwide or filtered by ISO-2 country, bounding box, or a point with a radius. Returns up to `limit` clusters ranked by relevance (corroborated and recent first). Use for 'is there a fire near X right now' or 'wildfires in <country> today'. Each cluster: position, first/last satellite pass (UTC), detections per sensor, peak fire radiative power (MW), confidence (possible | probable | corrobore = cross-checked with witnesses).
    ConnectorNo auth
  • Post a marketplace BUY request (POST /request) — you want to buy a resource; providers match against it and your escrow is debited on match. Bearer + a verified account (marketplace:write); an under-scoped token gets the backend's real 403. Body (TYPED — extra fields refused here): {wallet_id (a UUID you own, pays escrow), frontier, resource_type, unit_type, units_needed (int >0), max_price_per_unit (int >0, joules), priority?, requirements? (dict), ttl_seconds? (expiry), speed?, privacy_mode?, contract_escrow?, physical_claim?, provider_id?, rematch? (machine speed: {max_price_per_unit?, window_seconds?}), idempotency_key?}. Quote a specific request with `market_quote` before accepting a match. PHYSICAL TRADES: resource_type scene_stack, change_report, site_reconstruction or satellite_imagery MUST carry physical_claim {kind: physical_change|physical_state, site_lat, site_lng, t1, t0 (for a change), radius_m?} — the backend refuses the request without it; the trade is judged against a satellite frame at that site and date. ESCROW LANE: every trade's joules are held in escrow either way. The DEFAULT is the LEDGER LANE — escrow held in a system wallet and settled on the ledger (each settlement leg anchored on chain), NO on-chain contract and no contract fee; the match reads `escrow_bsv_state: "NO_CONTRACT"`, which is the normal, terminal state of that lane, not a failure. Set `contract_escrow: true` to opt in to the on-chain escrow contract lane for a flat contract fee added to your lock; the contract is mandatory for large trades. It takes effect ONLY where an oracle backs the trade (large enough to attract oracle verification, or an oracle-verified provider): a non-oracle opt-in falls back to the ledger lane with no contract and no fee, and the match returns `contract_escrow: false` plus a `contract_note` saying why. Fee and thresholds: https://raree.ai/llms.txt (not restated here). After settlement, `trade_settlement` shows the contract's own legs in its `contract` section (null on a ledger-lane trade).
    ConnectorNo auth
  • Per-minute price of calling a country, or a specific number, from a web browser with InternationalCall.co: the live rate, whether the free welcome credit covers a first call, how billing works, and a link that opens the dialer set to that country. Use it when someone asks what a call abroad costs or how to call a phone abroad from a computer. For which digits to dial, use get_dialing_instructions instead. Pass `destination` for the country's standard rate, or `number` to price that exact number: premium, satellite-adjacent and special-service ranges cost more than the standard rate (a local-format number also needs `destination`). The rate depends only on the number called, not on where the caller is.
    ConnectorNo auth
  • The image stack — an ORDERED STACK of dated Sentinel-2 ARCHIVE stills of ONE site across a date range (the place across time). Pose = lat/lng OR entity_type+id (anchor), the same pose rule as `look_at`. `t0` (YYYY-MM-DD, on or after 2015-06-23) and optional `t1` (default today) bound the range; `max_frames` (1-12, default 6) cuts it into that many equal windows, ONE still per window — the newest scene ACQUIRED inside that window with cloud cover at or under `max_cloud` (0-100, default 20). Each frame says its own `as_of` (the SCENE's date — never the window, never your request), `cloud_cover`, `scene_id`, `provenance` (provider, source_tier "provider", freshness "archive", attribution, gsd_m 10, extent_km 5.12), its own `charged_joules`, and the still as `image_jpeg_base64`. A window with no cloud-free scene is an explicit `available:false` frame with `as_of:null` and `charged_joules:0` — NEVER a fabricated image, never a scene borrowed from another window. Satellite-still resolution (10 m), not street-level. It does NOT say what changed between frames. AGENT KEYS ONLY (a browser session is refused BEFORE any charge). SIDE EFFECTS: none beyond the charge — read-only; stills are cached by pose + scene date (look_at's cache). ⚠ CHARGING: priced PER STILL at look_at's price; the meter RESERVES for `max_frames` before the stack is fetched and SETTLES for the frames DELIVERED (no frame at all settles to 0; a 4xx releases the reservation). Quote first: `billing_quote("/api/v1/look.through")` with max_frames. The JSON carries top-level `charged_joules` (what you kept paying, all-in) and a `price` block (per_frame_base_joules, max_frames, frames_delivered); verify any charge with `billing_attempts`. Every call through this relay carries a fresh idempotency key, so a retry here is always a new charge.Metered: charged to your own wallet — see the server instructions (CHARGING); quote first with `billing_quote`.
    ConnectorNo auth
  • skypeek: Predict satellite passes over a location. For sun and moon times use sun_moon_times. Returns the passes of a satellite (default the ISS) over a point in the next 1-3 days: start, highest and end times with azimuth and elevation, duration, and whether the pass is visible to the eye. SGP4 predictions, not observations, from CelesTrak orbital elements (only derived pass times are returned; no endorsement by CelesTrak implied). Satellites: CelesTrak's 'stations' and 'visual' groups plus NOAA 15 / 18 / 19; another NORAD id is a 422 (not charged). At most 40 passes. A cold orbital-data cache or an upstream outage can be a 503 (not charged; retry). Typically under 1 s; with a cold orbital-data cache up to a minute or more (a 503 when too slow, not charged: retry). Price: USD 0.002. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/iss-pass-times-api.html
    ConnectorNo auth
  • skypeek: Predict satellite passes over a location. For sun and moon times use sun_moon_times. Returns the passes of a satellite (default the ISS) over a point in the next 1-3 days: start, highest and end times with azimuth and elevation, duration, and whether the pass is visible to the eye. SGP4 predictions, not observations, from CelesTrak orbital elements (only derived pass times are returned; no endorsement by CelesTrak implied). Satellites: CelesTrak's 'stations' and 'visual' groups plus NOAA 15 / 18 / 19; another NORAD id is a 422 (not charged). At most 40 passes. A cold orbital-data cache or an upstream outage can be a 503 (not charged; retry). Typically under 1 s; with a cold orbital-data cache up to a minute or more (a 503 when too slow, not charged: retry). Price: USD 0.002. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/iss-pass-times-api.html
    ConnectorNo auth
  • Before/after satellite comparison of the same area on two dates from NASA GIBS true-color imagery (MODIS or VIIRS, about 250 m per pixel): one side-by-side JPEG with date labels plus pixel-based change metrics (share of changed pixels, brightness change) and a cloud, haze and snow estimate for each date, with a plain-language reading that says whether the change is likely real or just weather. For floods, wildfires and burn scars, drought and lake levels, snow cover, deforestation or construction at regional scale. Params: place ("Valencia, Spain") or lat + lon + radius_km (5 to 500, default 50) or bbox, date_before (default one year before date_after), date_after (default yesterday), layer, width (64 to 768 per image, default 384), include_separate. Price: $0.013 USDC per call, paid inside this MCP call via x402 (USDC on Base, Solana, Polygon or Arbitrum). x402 MCP clients such as @x402/mcp pay automatically. Free sample: call with the example input {"lat":-18.75,"lon":-67.1,"radius_km":50,"date_before":"2014-05-10","date_after":"2016-05-10","width":256}.
    ConnectorOAuth
  • skypeek: Get a recent satellite image of a place or coordinates. For the forecast use get_weather. Returns a recent satellite picture of a place as a base64 PNG, with the capture date, cloud cover, source and attribution: the least cloudy recent Sentinel-2 L2A scene at 10 m per pixel as true colour, NDVI (vegetation) or NDWI (water), clouds painted grey in the index views; NASA GIBS true colour (about 250 m) for areas wider than 10 km or when Sentinel-2 has no scene. Not real time (`date` is the scene day); clouds can hide the ground (404 too_cloudy, no_scene, no_imagery: not charged). Sentinel-2 data is free to use with credit; NASA GIBS has no restrictions. Not for navigation or safety. Typically 5 to 25 s (a few Sentinel-2 tiles are read and rendered). Price: USD 0.01. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/satellite-image-api.html
    ConnectorNo auth
  • skypeek: Get a recent satellite image of a place or coordinates. For the forecast use get_weather. Returns a recent satellite picture of a place as a base64 PNG, with the capture date, cloud cover, source and attribution: the least cloudy recent Sentinel-2 L2A scene at 10 m per pixel as true colour, NDVI (vegetation) or NDWI (water), clouds painted grey in the index views; NASA GIBS true colour (about 250 m) for areas wider than 10 km or when Sentinel-2 has no scene. Not real time (`date` is the scene day); clouds can hide the ground (404 too_cloudy, no_scene, no_imagery: not charged). Sentinel-2 data is free to use with credit; NASA GIBS has no restrictions. Not for navigation or safety. Typically 5 to 25 s (a few Sentinel-2 tiles are read and rendered). Price: USD 0.01. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/satellite-image-api.html
    ConnectorNo auth
  • Fusionne le contact satellite_lead_id DANS le contact principal master_lead_id (deux fiches de la même personne), avec la fonction de l'application : conversations re-pointées sur la principale (en cas de collision de canal, l'une est archivée, aucun message n'est supprimé), tags, notes et événements réunis, fiche principale complétée sans rien écraser, la fiche satellite quitte les listes. Réversible avec ficiel_unmerge_leads tant que rien n'est purgé : le merge_id renvoyé sert à défaire. Les chaînes de fusion sont interdites. Une fusion à tort mélange deux historiques de conversation. confirm doit valoir true, c'est la confirmation explicite. N'envoie aucun message. Portée « write » requise.
    Connector
    Destructive
    API key
  • Temporal anomaly watch: current event counts vs day-of-week and seasonal baselines, scored by z-score severity. Surfaces where activity is statistically abnormal right now — news velocity, satellite fire detections, and other tracked streams are compared against 90-day Welford baselines keyed by weekday and month, so a Tuesday in July is only compared to prior Tuesdays in July. Each anomaly carries the observed count, expected baseline count, z-score, multiplier, and a severity band (medium >= 1.5σ, high >= 2σ, critical >= 3σ). Filter by stream type, region, or minimum severity. An empty anomaly list with fresh data means activity is within normal bounds — that is itself signal. Statistical deviations per stream only: no story content, no cross-domain alert rollup. Seeded-cache read: weight 1 on API plans, included in the signed-in free allowance.
    ConnectorOAuth