"Orbit Sentinel - Satellite or Space Monitoring System" matching MCP tools:

• check_ground_motionA

  ground-motionA

  Measured ground motion (sinking/uplift) for a US address or lat/lon, in mm/year AND in/year, from NASA OPERA Sentinel-1 InSAR. Costs $0.40 from your SibFly credits; out-of-coverage / too-stale / too-low-confidence / fuzzy-geocode return FREE. Use the gate params to avoid paying for data you'd reject. dry_run=true is a FREE coverage+cost preview.

  ConnectorNo auth

• emem_askA

  emem, the verifiable memory protocol for the physical worldA

  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"}

  ConnectorNo auth

• get-space-documentA

  docuwriterA

  Use this when the user wants to read the full markdown content of a specific Space document/page after search or listing. Read-only: returns the selected document without changing content. Requires the document ID from list-space-documents, search-space-documents, or global-search.

  ConnectorOAuth

• query_space_satellite_filings_v1A

  osintA

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

  ConnectorNo auth

• preview_sync_planA

  GrowomatA

  Dry run: compute what a sync would import / export / remove for the active Space, without executing. Use before trigger_sync to see the blast radius. Honours the same campaign_ids hard scope and force as trigger_sync, and returns a planHash you can pass to trigger_sync (plan_hash) to execute exactly this plan or fail on drift. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

  ConnectorAPI key

• export-space-items-markdownA

  docuwriterA

  Use this when the user wants a Markdown export of selected Space pages, folders, or docs that can be returned in the MCP response. Read-only: returns merged Markdown without changing Space content. Use browser guidance for PDF, ZIP, or download-only export flows.

  ConnectorOAuth

• request_bookingA

  orbitA

  Stellt eine UNVERBINDLICHE Buchungsanfrage an das Orbit-Team. Die Anfrage reserviert den Slot noch NICHT — das Team prüft sie und bestätigt per E-Mail an die Kontaktadresse. Prüfe vorher mit check_availability, ob die gewünschten Slots frei sind, und nenne dem Menschen den Preis aus quote_booking. Raum-IDs aus list_rooms, Service-IDs aus list_services.

  ConnectorNo auth

• delete-space-repository-linkA

  docuwriterA

  Use this when the user wants to remove an Autopilot repository link from a Space. Destructive external-provider action: deletes the link after authorization and may remove provider webhook configuration. Requires Enterprise access, manageable Space permission, space_id, and link_id.

  Connector

  Destructive

  OAuth

• iss_nowA

  Open NotifyA

  Current latitude / longitude of the International Space Station.

  ConnectorNo auth

• morse_decodeA

  NatoA

  Decode Morse code back to text. Accepts letters separated by spaces and words by "/" or " " (double space). Keyless, offline.

  ConnectorNo auth

• search_spacesA

  publicA

  Find the most relevant published DSGHT future-space by keyword (topic + report text, plain-text ranked, no AI). Use this to locate a space before calling get_public_scenarios / get_public_tensions / get_public_report when you do not already know the slug.

  ConnectorNo auth

• brainkb_list_spacesA

  brainkbB

  List spaces the user can see (their own/member spaces + public ones), each annotated with THIS caller's permission so you know what they may do: - your_role: 'owner' | 'editor' | 'viewer' | null (their space membership) - is_owner: they own the space - access: 'owner' | 'member' | 'public' (how it's available to them) - can_write: their space role permits ingest (owner/editor) — a real ingest also needs the 'ingest' capability + any per-space access rules. Use this to tell the user which spaces they can read vs. write vs. only see as public.

  ConnectorNo auth

• get_active_spaceA

  GrowomatA

  Report the MCP server's current active Space binding. Returns { active_space_id, source, name?, role?, type?, campaign_count? }. source is 'env' (set at start-up via GROWOMAT_SPACE_ID), 'set_active_space' (changed at runtime), or 'default' (unbound — the BE falls back to the caller's Personal Space). No API round-trip when nothing is bound.

  ConnectorAPI key

• get_lightning_activityA

  Smarter WeatherA

  Real-time lightning near a location: GLM satellite flash count (30km/10min) and MRMS ground-truth lightning density + 30-minute probability. The summary field is ready-to-use. A zero flash count means no lightning inside that window -- report it as a quiet observation scoped to the window in `scope`, never as a data gap. Only call when storms may be active or the user asks about lightning. Example: {"location": "Tampa"}.

  ConnectorNo auth

• global-searchA

  docuwriterA

  Use this when the user wants to search documents across every accessible Space rather than one known Space. Read-only: returns matching titles, snippets, Space details, and URLs for a query without changing content.

  ConnectorOAuth

• create-space-documentA

  docuwriterA

  Use this when the user wants to create a markdown document/page in a Space from provided content. State-changing: creates the document directly after authorization. Requires numeric space_id, title, and markdown content. Use create-space-item for folders or external links.

  ConnectorOAuth

• delete-space-documentA

  docuwriterA

  Use this when the user explicitly wants to delete one existing Space document/page. Destructive state-changing action: deletes the document directly after authorization. Requires the document ID from list-space-documents or search results; use delete-space-items for folders or bulk item deletion.

  Connector

  Destructive

  OAuth

• enable-space-repository-linkA

  docuwriterA

  Use this when the user wants to turn on or resume an existing Autopilot repository sync link for a Space. State-changing external-provider action: enables the link and registers the provider webhook after authorization. Requires Enterprise access, manageable Space permission, provider access, space_id, and link_id.

  ConnectorOAuth

• disable-space-repository-linkA

  docuwriterA

  Use this when the user wants to pause, turn off, or disable an Autopilot repository link for a Space. State-changing external-provider action: disables the link and attempts to remove the provider webhook after authorization. Requires Enterprise access, manageable Space permission, space_id, and link_id.

  ConnectorOAuth

• bulk-manage-space-suggestionsA

  docuwriterA

  Use this when the user wants to apply or discard multiple Autopilot/repository-sync suggestions at once. Destructive state-changing action: bulk apply can update multiple Space documents, and bulk discard removes suggestions from active review after authorization. Requires suggestion IDs from list-space-suggestions; bulk apply requires Enterprise access.

  Connector

  Destructive

  OAuth

• adw.adw_594A

  AlpineDataWorks Intelligence ServerB

  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