"Satellite" matching MCP tools:

• query_space_satellite_filings_v1

  osint

  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). Status and lifecycle updates on the filings that ARE here continue to flow daily. 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).

  Connector

• outdoor_recreation_economy

  Bea Gov

  MARKET SIZE for outdoor recreation activities in US dollars, by activity and state — BEA's Outdoor Recreation Satellite Account (official government statistics, not analyst estimates). Use for "how big is the hunting industry", "fishing economy by state", "which states have the largest outdoor recreation economy", "value of the skiing industry". Activities include hunting, shooting, fishing, boating, hiking/camping, equestrian, skiing/snow, bicycling, RVing, motorcycling/ATV, golf/tennis, guided tours, and the overall total. Returns value added (the activity's contribution to GDP) per state for a year, ranked. IMPORTANT: birdwatching and wildlife WATCHING are not separate lines in this account — hunting and fishing are the only wildlife-related activities measured, so do not use this to size birding specifically. This tool wraps BEA table SAOACTVA so you do not have to know BEA table or line codes; for other BEA data use get_data.

  Connector

• open_voice_bridge

  Sats4AI - Bitcoin-Powered AI Tools

  TEMPORARILY UNAVAILABLE OVER MCP — create_payment refuses this tool, so you will not be charged. Use the L402 HTTP endpoint instead: POST https://sats4ai.com/api/l402/voice-bridge/open (same service and pricing, pay the 402 challenge), or use ai_call for a fully-managed agent call over MCP. Open a Voice Bridge session: a live phone call where YOUR LLM is the brain. Sats4AI provides PSTN + streaming STT + TTS as composable primitives. You decide when to speak (call voice_bridge_say), you read transcripts as they arrive (call poll_voice_bridge), you close the call when done (call end_voice_bridge). Unused deposit time is refunded via LNURL-withdraw. Use this when you want to keep your conversation context private and drive each turn yourself. When NOT to use: not for fully-managed agent-style calls where we handle the brain (use ai_call). Not for one-shot TTS broadcasts or IVR playback (use place_call). Not when live transcript polling adds no value — the per-turn overhead isn't worth it. Privacy: transcripts held in memory only, garbage-collected 30 minutes after the call ends; call audio is never persisted. Pay with Bitcoin Lightning — no telecom account, no signup. Requires create_payment with toolName='voice_bridge_open', phoneNumber, durationMinutes. Deposit is priced per destination off the carrier rate sheet and is BTC-pegged, so call create_payment for the exact figure; premium-rate and satellite ranges are refused.

  Connector

• fcc_regulation

  Fcc Regulations

  Get the full text of one FCC regulation — a US Federal Communications Commission rule codified in 47 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does 47 CFR 15 require", "what is the FCC rule for X", "does the FCC allow X", "read 47 CFR 15.247", "the FCC RF emissions limit". Forgiving citation input: "15.109", "47 CFR 15.109", "§15.247", "15.247(b)" (paragraph stripped to the section), "Part 97". Covers telecommunications regulation across all of Title 47: Part 15 unlicensed devices and RF emissions limits, Part 97 amateur radio, Part 2 equipment authorization and frequency allocations, Part 73 broadcast radio and TV, Part 76 cable, Part 25 satellite, Parts 24/27 wireless and spectrum, Part 64 common carrier and telephone rules, Part 11 emergency alert system, Part 9 911. Also accepts common names: "amateur radio", "unlicensed devices", "equipment authorization", "RF exposure limits". Pass a whole part (e.g. "15" or "Part 97") to get that part's section list. Example: fcc_regulation({ citation: "15.109" }) -> radiated emission limits; fcc_regulation({ citation: "97.301" }) -> amateur radio authorized frequency bands. Keyless. This pack is the FCC RULES text; the separate `fcc` and `data-fcc` packs serve FCC filings and licensing data (ULS licenses, ECFS comments, broadband maps).

  Connector

• adw.adw_594

  AlpineDataWorks Intelligence Server

  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.

  Connector

• fcc_regulations_search

  Fcc Regulations

  Keyword search across the FCC regulations — US telecommunications rules in 47 CFR. Answers "what FCC regulations cover X", "the FCC rule about X", "find the telecommunications regulation for X", "which radio / spectrum / wireless rule applies to X". Great for topics: unlicensed device emission limits, Part 15 intentional and unintentional radiators, RF exposure and radiofrequency radiation limits, equipment authorization and certification, amateur radio operating privileges, spectrum and frequency allocations, broadcast station licensing and ownership, cable and satellite carriage, robocalls and caller ID, 911 and emergency alerting, wireless and common carrier obligations. Returns matching FCC rules with citation (47 CFR), heading, excerpt, and source URL. Example: fcc_regulations_search({ query: "unlicensed device emission limits" }); fcc_regulations_search({ query: "amateur radio frequency bands", limit: 15 }). Keyless. Searches the FCC RULES text; the separate `fcc` and `data-fcc` packs search FCC filings and licensing data.

  Connector

• astronomy_get_satellite_passes

  astronomy-mcp-server

  Predict visible passes of a satellite (e.g. the ISS, NORAD 25544) over an observer in the next `days`. Identify the satellite by exactly one of `norad_id` or `name` — supplying both, or neither, is rejected. `name` is matched as a case-insensitive substring of CelesTrak's catalog names, so it resolves only when it picks out a single object: a broader query comes back with the matching objects and their catalog numbers to choose from, and the result echoes the query that resolved it as `resolved_from_name`. Fetches the object's current GP element set from CelesTrak, propagates it with SGP4 in-process, and returns each pass's rise, peak, and set times with azimuths and the peak elevation. Only passes that are naked-eye-plausible are returned — the satellite must be sunlit at peak while the observer's sky is dark. Every returned pass rises within the requested window: a pass already underway at `start` is omitted rather than reported with `start` as its rise, so back up `start` to see it. A `start` further than about a month from the element set's epoch is rejected as out of range on that distance alone, and an element set that will not propagate to a window inside that horizon is rejected as a reentry — so an empty `passes` means only that nothing was visible. CelesTrak publishes only current element sets, so in practice `start` must be within about a month of today. NORAD catalog numbers and catalog names are found at celestrak.org or heavens-above.com. This is a gated, network-backed extension (CelesTrak is keyless but rate-limited; element sets are cached briefly). Default elevation 0 m; pass an IANA timezone for observer-local pass times.

  Connector

• get_broadband_by_location

  FCC Broadband Map

  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

• get_group

  Celestrak

  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

• emem_ask

  emem, the verifiable memory protocol for the physical world

  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. Example arguments: {"q":"is this neighbourhood flood-prone for a flat purchase","place":"Ashok Nagar, Ranchi"}

  Connector

• get_visual_passes

  N2yo

  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

• adw.adw_395

  AlpineDataWorks Intelligence Server

  Returns a 0-100 US cooling-demand grid-stress index (smart-grid load anomalies fused with satellite land-surface-temperature anomalies, seasonal baseline back to 1895) with stress_score, load_anomaly, lst_anomaly, transformer_risk_flag, confidence, and methodology_version. Call when the user asks about heatwave grid strain, urban-heat-island load risk, or transformer-failure exposure, or when timing maintenance dispatch, crew pre-staging, or summer O&M budget decisions. Updates: daily.

  Connector

• get_satellite

  Celestrak

  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

• create_3d_listing

  ParcelLaunch — 3D property listings from an address

  Build a cinematic, interactive 3D flyover listing of a real property from a street address (or a parcel/APN number) — with the parcel boundary drawn on the terrain. Takes about a minute. Returns a free watermarked preview link the user can open on any phone, plus the link to unlock the clean, brandable version. Use this for raw land, acreage, odd lots, waterfront and new-construction dirt — anywhere a flat satellite photo undersells the property.

  Connector

• set_link_targets

  Epovest

  Set the addresses of the brand that are neither its canonical website nor a page of the surface registry: a satellite domain the customer does not want to keep aligned, a tracking link, a partner page. They are set ONCE for the project and serve every line of the corroboration registry, present and future, so there is nothing to set line by line. The list you send REPLACES the previous one, and the answer returns what the project now holds, derived addresses included: read it back to confirm. An empty list keeps only the derived ones. Call get_link_targets first, and confirm with the user before replacing.

  Connector

• get_light_pollution

  Stellarhound — stargazing forecasts, dark-sky sites & aurora

  Estimate light pollution at any point: approximate Bortle class and what's visible there. Use for "how dark is the sky at X" / "can I see the Milky Way from X". Returns the zenith-brightness-derived estimate (mpsas, approximate Bortle class) and a plain-language ceiling: what the Milky Way, naked-eye and telescope views are like under that sky. This is a satellite-data estimate, not a field measurement — say so. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). Returns {light_pollution:{bortle_approx, mpsas, ceiling:{label, milky_way, naked_eye, telescope}, note}, attribution}.

  Connector

• get_positions

  N2yo

  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

• adw.adw_130

  AlpineDataWorks Intelligence Server

  Returns a 0-100 geomagnetic activity risk score (daily composite z-score of NOAA SWPC planetary Kp peak, mean, and trend; 10-year history) with score, percentile, trend, and methodology_version. Call when the user asks about space weather, geomagnetic storms, Kp index, solar storms, or aurora conditions, or when timing satellite maneuvers, thruster burns, ground-station uplinks, GNSS/GPS accuracy, or HF radio operations. Updates: daily.

  Connector

• fieldpulse

  pulsenetwork

  FieldPulse: Global precision agriculture intelligence API. Synthesizes satellite NDVI data, Open-Meteo soil/weather data, USDA WASDE, FAO, and EPPO into structured, actionable intelligence for growers, agronomist Coverage: Global Endpoints: • yield-forecast ($0.15): Yield and production forecast for any crop and region • weather-risk ($0.08): 7-day crop-specific weather risk assessment • soil-intel ($0.08): Observed soil wetness and computed evapotranspiration intelligence • pest-disease ($0.10): Pest and disease risk assessment with outbreak alerts • irrigation ($0.08): ET0-based irrigation recommendation and water budget • commodity-outlook ($0.10): Agricultural commodity market outlook and price intelligence • input-cost ($0.08): Fertilizer, seed, and crop protection cost intelligence • planting-window ($0.05): Optimal planting window from air temperature, soil wetness and frost dates • season-brief ($0.20): Comprehensive seasonal agricultural intelligence brief • crop-health ($0.10): Crop health assessment from satellite + soil data

  Connector

• calculate

  D Fetcher

  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