Skip to main content
Glama
213,524 tools. Last updated 2026-06-19 18:25

"Satellite" matching MCP tools:

  • Full space-weather now-cast (NOAA SWPC) — the NOAA R/S/G storm scales (radio blackout / radiation storm / geomagnetic storm), geomagnetic Kp index, solar wind (speed, density, and Bz — the storm driver), the latest solar X-ray flux / flare, and an aurora-visibility hint. Affects satellite comms & drag, GPS accuracy, HF radio, power grids, and the radiation/power environment for orbital compute. Use for "is there a geomagnetic/solar storm right now".
    Connector
  • Per-band satellite-and-sensor fleet inventory — names the upstream platform (e.g. Sentinel-2A/B, MODIS Aqua/Terra, Landsat-8/9), revisit cadence, native resolution, and license for every materialized band. Lets an agent attribute imagery products correctly and pick the right band when revisit cadence matters. When to use: Call when the user asks 'which satellite is this from', 'what's the revisit time', or needs source attribution for a derived answer. Pair with emem_materializers for the wire path and emem_sources for the connector-level metadata.
    Connector
  • Get satellite orbital elements (TLE / GP data) for a single object by NORAD catalog ID. Returns orbital parameters: inclination, eccentricity, mean motion, RAAN, argument of perigee, epoch, and derived orbital period in minutes. norad_id 25544 = ISS, 20580 = Hubble. This is the orbital catalog, not live position tracking.
    Connector
  • Get broadband providers and availability at a specific lat/lon location. Returns a list of broadband providers serving the location with their advertised download/upload speeds and technology types. Includes BEAD classification (unserved/underserved/served) based on max available speeds. NOTE: The FCC Broadband Map API has bot protection and may reject requests. If you get an error, the API endpoint may have changed. The FCC updates this API frequently without notice. Args: latitude: Location latitude (e.g. 38.8977 for Washington DC). longitude: Location longitude (e.g. -77.0365 for Washington DC). technology_code: Filter by technology (0=All, 10=Copper, 40=Cable, 50=Fiber, 60=Satellite, 70=Fixed Wireless). speed_download: Minimum download speed in Mbps (default 25). speed_upload: Minimum upload speed in Mbps (default 3). as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).
    Connector
  • Active US wildfires from NIFC WFIGS — incident name, size in acres, % contained, cause, state and location. The 'how big / how contained' detail satellite hotspot feeds can't give (pairs with natural_events, which has global fire points but not size/containment). Largest first. Args: state: optional US state filter, e.g. CA, TX (2-letter). only_uncontained: only fires below 100% containment. min_acres: minimum incident size in acres. limit: max results.
    Connector
  • List orbital elements (TLE / GP data) for an entire CelesTrak group — e.g. the Starlink, GPS, or weather satellite catalog. Groups: "stations", "starlink", "gps-ops", "weather", "science", "geo", "active". Returns up to 100 satellites with orbital parameters (inclination, eccentricity, period). Catalog/orbital data, not live tracking.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • N2YO MCP — wraps the N2YO Satellite Tracking REST API (n2yo.com)

  • CelesTrak MCP — satellite orbital elements (TLE / GP data) for any tracked object.

  • Single-shot free-text answer about a real-world location, backed by signed satellite/elevation/water/built-up receipts. Forwards a place mention plus a question; runs the locate → recall → algorithm chain server-side; returns one packaged envelope. When to use: Use when the question concerns a specific real-world place and a packaged, citation-bearing answer is preferable to manual primitive composition. Forward the user's question verbatim as `q` plus the location as `place` (free text), `cell` (cell64), or `lat`+`lng`. The server resolves the location, classifies the question to a topic, recalls every relevant band (auto-materializing Sentinel-2 / Sentinel-1 / Cop-DEM / JRC GSW / Overture / weather on miss), surfaces the algorithm recipes that compose those bands into named scores, and returns a single envelope with `topic_routing`, `facts`, `algorithms_for_question`, an optional Sentinel-2 RGB scene URL, and a `caveats` block (grid resolution, revisit cadence). All facts are signed by the responder; the signed `receipt` (and its content-addressed `fact_cids`) is surfaced at the envelope ROOT — `response.receipt` / `response.fact_cids` — exactly like every other primitive, and is also mirrored under `facts_summary.receipt` for back-compat. Set `include_image: true` to bundle the latest cloud-free Sentinel-2 thumbnail. Out-of-scope questions return `topic_routing.matched_topic: null` plus the full inventory so the caller can route elsewhere.
    Connector
  • Search the satellite catalog by name substring and return matching orbital elements (TLE / GP data). e.g. "STARLINK", "NOAA", "GPS". Returns up to 50 matches with orbital parameters (inclination, eccentricity, period). Catalog/orbital data, not live tracking.
    Connector
  • Track where a satellite is right now (or in the next few seconds): get its live latitude, longitude, altitude, and look-angles (azimuth/elevation) from an observer on Earth. Use this to answer "where is the ISS right now?" (NORAD id 25544) or to locate any satellite by NORAD id. Example: get_positions({ norad_id: 25544, lat: 40.71, lon: -74.0 }).
    Connector
  • Real-time position of ANY satellite by its NORAD id OR a common name — computed with SGP4 from the latest live TLE: exact latitude/longitude, altitude, velocity, ground-footprint radius, the speed-of-light latency floor, and how old the TLE is. Use for "where is the ISS / Hubble right now" or to get a precise sub-satellite point. This is the TRUE propagated position, not an approximation. Args: norad_id: NORAD catalog number (e.g. 25544 = ISS, 20580 = Hubble, 44714 = a Starlink). name: a common name instead of the id — "ISS", "Hubble", "Tiangong". Pass one of norad_id or name. track_minutes: also return a predicted ground-track this many minutes ahead (0 = just the current position; max 360). step_seconds: ground-track sampling step in seconds (default 60).
    Connector
  • Get list of broadband providers serving a county. Returns provider names, technology types, and speed tiers available in the specified county. Useful for BEAD applications to identify which providers serve an area and what technologies they deploy. Args: county_fips: 5-digit county FIPS code (e.g. '11001' for Washington DC, '53033' for King County WA). Always a string, never an integer. technology_code: Filter by technology (0=All, 10=Copper, 40=Cable, 50=Fiber, 60=Satellite, 70=Fixed Wireless). speed_download: Minimum download speed threshold in Mbps (default 25). speed_upload: Minimum upload speed threshold in Mbps (default 3). as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).
    Connector
  • Name: MissingBias_Detector Description: A specialized diagnostic engine used to detect Missing Not At Random (MNAR) and Missing At Random (MAR) patterns in datasets. This tool determines if the "missingness" of data in a primary variable is statistically dependent on the values of a secondary covariate. Use this to determine whether missing data can be safely deleted or if it requires advanced imputation to avoid systematic bias in downstream models. Why This Tool is Mandatory for Data Cleaning Prevents Selection Bias: Identifying bias ensures that the agent does not inadvertently delete a specific sub-population (e.g., an unreliable sensor that only fails at high temperatures). Automated Strategy Selection: Provides the statistical evidence needed to choose between Deletion (if no bias is found) and Imputation/Source Investigation (if bias is detected). Math Error Prevention: Offloads complex dependency testing (like Little’s MCAR test or logistic modeling of missingness) to a dedicated engine, eliminating LLM calculation errors. Operational Logic The tool analyzes a dictionary containing two aligned arrays: Target Array (Index 0): The variable containing missing values (null, NaN, or empty strings). Predictor Array (Index 1): The potential biasing variable used to see if its values influence the probability of the Target Array being missing. Recommended Workflows Exploratory Data Analysis (EDA): Run this on all permutations of columns to identify hidden dependencies in a new dataset. Hardware/Sensor Audits: Identify "unreliable sources" (e.g., which satellite sensor or survey researcher is producing the most incomplete data). Pre-Training Validation: Ensure that "dropping rows" won't result in a biased training set that compromises model generalization. Interpretation of Results Bias Detected: You must not simply delete the missing rows. You must investigate the source of the bias or use statistical imputation. No Bias Detected: Missingness is likely stochastic; deleting rows is a statistically lower risk for analysis. Example Input: { "array_with missingness":["NA",166.445,470.604,25.0739,49.1652,324.7797,190.9287,"NA",451.39,405.4469,"NA",347.1129,253.0294,141.4462,"NA",241.4338,160.2388,123.1855,51.5936,151.8691,309.7825], "array_causing_bias":[418.3812,"NA",14.552,329.5427,"NA",119.1472,"NA",462.8084,320.5384,148.8701,412.0277,125.1991,"NA",255.8993,441.0706,"NA",297.2804,"NA","NA",296.7565,111.2001] } Example Output: {"missing_is_biased":[1]}
    Connector
  • Find when a satellite will be visible to the naked eye overhead from an observer location (visual passes = bright, sunlit passes against a dark sky). Returns start/max/end times, elevation, azimuths, brightness magnitude, and duration. Use this for "when can I see the ISS pass over?" Example: get_visual_passes({ norad_id: 25544, lat: 40.71, lon: -74.0 }).
    Connector
  • Get Starlink satellite info sorted by most recently launched. Returns spaceTrack data including object name, launch date, and decay date.
    Connector
  • Satellite/constellation catalog with each satellite's altitude, orbital period, and a derived speed-of-light round-trip latency to ground (the physics floor for orbital networks / data centers in space). Use for "how many Starlink satellites / orbital latency". Args: group: starlink, stations, gps-ops, oneweb, galileo, weather, active, geo, science. limit: max satellites in the sample.
    Connector
  • Fetch the Two-Line Element (TLE) set for a specific satellite by its NORAD catalog ID. Returns the satellite name, epoch date, and both TLE lines.
    Connector
  • Calculate vitamin D synthesis at a given location and time. Returns sun position, UV index, IU/min, minutes to reach the target dose, MED (sunburn threshold), the peak window, and optional 15-min day / monthly year curves. UV index uses a live satellite-driven forecast where available, with a clear-sky fallback.
    Connector
  • Search NASA's Common Metadata Repository for Earth-science dataset collections by keyword, platform (satellite/mission), instrument, time range, or bounding box. ~10k collections covering MODIS, Landsat, Sentinel, VIIRS, GPM, and every NASA DAAC. Sorted by usage. Keyless.
    Connector