Exoplanet Archive vs Server Everything
A side-by-side look at the Exoplanet Archive and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Exoplanet Archive for aerospace & astrodynamics work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Exoplanet Archive when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tap, planets, composite.
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aerospace & Astrodynamics | Other Tools and Integrations |
| Quality signal | 59/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 91,486 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Exoplanet Archive | View Server Everything |
Tools & capabilities
Exoplanet Archive tools 6
tapADQL TAP query. For "how many confirmed exoplanets" or any per-planet count, query `pscomppars` (one row per confirmed planet) or COUNT(DISTINCT pl_name) -- never a bare COUNT(*) FROM ps, which counts published parameter SOLUTIONS (several per planet, currently ~40k rows for ~6.5k planets) and silently over-counts by 6x. Prefer the dedicated confirmed_planet_count tool for planet-count questions.planetsPer-solution search against the `ps` (Planetary Systems) table -- one row per published parameter SOLUTION, with several solutions per confirmed planet. Good for comparing how a planet's measured parameters changed across papers; NOT a planet count or a clean per-planet list (its row count is parameter solutions, not planets). For planet counts or one-row-per-planet listings use `composite` or `confirmed_planet_count` instead.compositeComposite planet parameter table `pscomppars` -- one row per confirmed planet. Use this (or `confirmed_planet_count`) for "how many confirmed exoplanets" questions and for any per-planet listing; do not use `ps`/`tap` for those, since `ps` has several rows per planet.confirmed_planet_countCount of confirmed exoplanets -- from the composite parameter table `pscomppars` (one row per planet), not the per-solution `ps` table. Use this for "how many confirmed exoplanets" questions. Optional filter narrows the count, e.g. "disc_year = 2023" for planets discovered that year. Returns the unit and the date of the live query.kepler_candidatesKepler Object of Interest (KOI) candidate table -- unconfirmed candidates, not confirmed planets. Do not use this table's row count to answer a confirmed-planet-count question.microlensingMicrolensing event table -- detection events, not a planet count.
Server Everything tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Exoplanet Archive
{
"mcpServers": {
"exoplanet-archive": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-exoplanet-archive"
]
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Exoplanet Archive is categorized under Aerospace & Astrodynamics and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Exoplanet Archive for aerospace & astrodynamics work and Server Everything for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Exoplanet Archive has no declared pricing — check the project's own site. Server Everything is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add exoplanet-archive and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Exoplanet Archive has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Server Everything has 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars.