spaceship-mcp
npm
v0.3.0
Published by bartwaardenburg — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for managing domains, DNS records, and marketplace listings via the Spaceship API
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/update-checker.js:14`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch(`https://registry.npmjs.org/${packageName}/latest`); if (!response.ok)
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/update-checker.js
Each tool and what it can reach — statically extracted from the published source.
list_dns_recordsingests untrusted inputcheck_dns_alignmentno sensitive capabilitycheck_domain_availabilityno sensitive capabilitycreate_a_recordno sensitive capabilitycreate_aaaa_recordno sensitive capabilitycreate_alias_recordno sensitive capabilitycreate_caa_recordno sensitive capabilitycreate_checkout_linkno sensitive capabilitycreate_cname_recordno sensitive capabilitycreate_https_recordno sensitive capabilitycreate_mx_recordno sensitive capabilitycreate_ns_recordno sensitive capabilitycreate_ptr_recordno sensitive capabilitycreate_sellerhub_domainno sensitive capabilitycreate_srv_recordno sensitive capabilitycreate_svcb_recordno sensitive capabilitycreate_tlsa_recordno sensitive capabilitycreate_txt_recordno sensitive capabilitydelete_dns_recordsno sensitive capabilitydelete_personal_nameserverno sensitive capabilitydelete_sellerhub_domainno sensitive capabilityget_async_operationno sensitive capabilityget_auth_codeno sensitive capabilityget_contactno sensitive capabilityget_contact_attributesno sensitive capabilityget_domainno sensitive capabilityget_personal_nameserverno sensitive capabilityget_sellerhub_domainno sensitive capabilityget_transfer_statusno sensitive capabilityget_verification_recordsno sensitive capabilitylist_domainsno sensitive capabilitylist_personal_nameserversno sensitive capabilitylist_sellerhub_domainsno sensitive capabilityregister_domainno sensitive capabilityrenew_domainno sensitive capabilityrestore_domainno sensitive capabilitysave_contactno sensitive capabilitysave_contact_attributesno sensitive capabilitysave_dns_recordsno sensitive capabilityset_auto_renewno sensitive capabilityset_email_protectionno sensitive capabilityset_privacy_levelno sensitive capabilityset_transfer_lockno sensitive capabilitytransfer_domainno sensitive capabilityupdate_domain_contactsno sensitive capabilityupdate_nameserversno sensitive capabilityupdate_personal_nameserverno sensitive capabilityupdate_sellerhub_domainno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-08 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan spaceship-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.