Starfetch vs Server Everything
A side-by-side look at the Starfetch 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 Starfetch 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 Starfetch when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
starfetch_list_presets, starfetch_registry_search, starfetch_tap_availability.
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 | 60/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 | 2 | 91,486 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 12 | Not listed |
| Full listing | View Starfetch | View Server Everything |
Tools & capabilities
Starfetch tools 12
starfetch_list_presetsList built-in TAP service presets before selecting an explicit target for metadata inspection.starfetch_registry_searchSearch VO registry metadata when no built-in preset fits; inspect the selected service before querying it.starfetch_tap_availabilityCheck whether the selected TAP service reports itself available; an unavailable service is not an empty catalog result.starfetch_tap_capabilitiesInspect the selected TAP service's languages, formats, and authentication requirements before using service-specific features.starfetch_tap_tablesList tables on the selected TAP service before choosing an exact table for ADQL.starfetch_tap_columnsInspect names, datatypes, units, and descriptions for an exact metadata-discovered table before constructing ADQL.starfetch_tap_queryRun a small bounded synchronous TAP ADQL query after inspecting the exact table and columns. Use TOP in ADQL and/or maxrec, and treat tool errors as failures rather than empty scientific results.starfetch_tap_submit_jobSubmit metadata-backed bounded ADQL as an explicit TAP async job when synchronous querying is insufficient. Preserve the exact query and use starfetch_tap_query for small work.starfetch_tap_job_statusRead the current phase and links for a TAP async job.starfetch_tap_job_waitPoll a TAP async job until completion, timeout, or terminal failure. This is an explicit wait and never starts a background job.starfetch_tap_job_fetchFetch a TAP async job result. JSON and JSONL conversion supports VOTable, CSV, and TSV rows.starfetch_tap_job_deleteDelete a TAP async job from the remote service.
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.
Starfetch
{
"mcpServers": {
"starfetch": {
"command": "npx",
"args": [
"-y",
"@starfetch-js/mcp"
]
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Starfetch 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 Starfetch 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.
Starfetch 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 starfetch and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Starfetch has a quality signal of 60/100 (Good) with 2 views, 0 installs and 2 GitHub stars. Server Everything has 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars.