space-defense-osint
Related Servers
Alternatives to space-defense-osint
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that wraps the NASA Space-Track API to provide tools for TLE lookup, conjunction query, and satellite catalog search.-

Orbital Watchofficial
AlicenseBqualityCmaintenanceEnables MCP clients to look up tracked satellites and debris, analyze debris fields and constellations, find predicted close approaches, and retrieve NOAA space-weather scales, alerts, and plain-English impacts.5MIT- AlicenseNot gradedqualityBmaintenanceProvides satellite orbital elements (TLE / GP data) for any tracked object via MCP.418 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables discovery, analysis, and explanation of open satellite data through MCP, with support for STAC catalogs and NASA GIBS.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to search GitHub repositories and users, retrieve weather data and forecasts, and access NASA astronomy and image data through modular MCP tools.-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that equips LLM clients with authoritative astrodynamics tools including TLE/SGP4 propagation, Lambert solving, ground-station access, time-scale and coordinate-frame conversions, and more.59 PyPI2MIT
TDQS
Scored across 3 tools
Each tool targets a clearly different data source and task: space-weather Kp/alerts, NOTAM TFR geometry conversion, and satellite TLE/pass prediction. There is no meaningful overlap that would cause misselection.
All names use snake_case and follow a verb_source_or_data pattern: query_noaa_swpc_kp, analyze_notam_tfr, fetch_celestrak_tle. The differing verbs reflect genuinely different operations rather than inconsistent conventions.
Three tools is a reasonable minimal set, and each has a distinct purpose. For a broad 'space-defense-osint' server it still feels somewhat thin, but the count is not excessive or clearly mismatched.
The surface provides only narrow primitives: current Kp/alerts, a NOTAM Q-line conversion, and a single TLE pass prediction. It lacks obvious OSINT operations such as fetching NOTAM/TFR records, querying multiple satellites, historical/forecast space weather, or cross-source correlation.