Horizons Nasa vs Starfetch — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Horizons Nasa vs Starfetch
In-depth architectural comparison of the Horizons Nasa and Starfetch MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Horizons Nasa
Aerospace & Astrodynamics · Local stdio
Quality: 32/100 (Emerging) | Auth: No auth required
Starfetch
Aerospace & Astrodynamics · Local stdio
Quality: 39/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Horizons Nasa if you need specialized Aerospace & Astrodynamics tools running via a local process. Choose Starfetch if your workspace requires Aerospace & Astrodynamics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
H
Choose Horizons Nasa when:
You need dedicated capabilities in the Aerospace & Astrodynamics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Horizons Nasa is categorized under Aerospace & Astrodynamics and uses a local stdio subprocess. In contrast, Starfetch belongs to Aerospace & Astrodynamics using local stdio subprocess. Select Horizons Nasa when you need capabilities focused on aerospace & astrodynamics and Starfetch when you require tools for aerospace & astrodynamics.