Spaceship (bartwaardenburg) MCP Server

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

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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:

PointsAdoption-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.

Findings 1

medium Hardcoded egress to an external endpoint (dist/update-checker.js)MTC-SRC-003

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

Tools 48

Each tool and what it can reach — statically extracted from the published source.

  • list_dns_recordsingests untrusted input
  • check_dns_alignmentno sensitive capability
  • check_domain_availabilityno sensitive capability
  • create_a_recordno sensitive capability
  • create_aaaa_recordno sensitive capability
  • create_alias_recordno sensitive capability
  • create_caa_recordno sensitive capability
  • create_checkout_linkno sensitive capability
  • create_cname_recordno sensitive capability
  • create_https_recordno sensitive capability
Show 38 more tools ↓
  • create_mx_recordno sensitive capability
  • create_ns_recordno sensitive capability
  • create_ptr_recordno sensitive capability
  • create_sellerhub_domainno sensitive capability
  • create_srv_recordno sensitive capability
  • create_svcb_recordno sensitive capability
  • create_tlsa_recordno sensitive capability
  • create_txt_recordno sensitive capability
  • delete_dns_recordsno sensitive capability
  • delete_personal_nameserverno sensitive capability
  • delete_sellerhub_domainno sensitive capability
  • get_async_operationno sensitive capability
  • get_auth_codeno sensitive capability
  • get_contactno sensitive capability
  • get_contact_attributesno sensitive capability
  • get_domainno sensitive capability
  • get_personal_nameserverno sensitive capability
  • get_sellerhub_domainno sensitive capability
  • get_transfer_statusno sensitive capability
  • get_verification_recordsno sensitive capability
  • list_domainsno sensitive capability
  • list_personal_nameserversno sensitive capability
  • list_sellerhub_domainsno sensitive capability
  • register_domainno sensitive capability
  • renew_domainno sensitive capability
  • restore_domainno sensitive capability
  • save_contactno sensitive capability
  • save_contact_attributesno sensitive capability
  • save_dns_recordsno sensitive capability
  • set_auto_renewno sensitive capability
  • set_email_protectionno sensitive capability
  • set_privacy_levelno sensitive capability
  • set_transfer_lockno sensitive capability
  • transfer_domainno sensitive capability
  • update_domain_contactsno sensitive capability
  • update_nameserversno sensitive capability
  • update_personal_nameserverno sensitive capability
  • update_sellerhub_domainno sensitive capability

What this scan could not see

Versions 1

Scan 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.

VersionScoreFindingsEngineScanned
v0.3.0 latest A 96/100 1 1.13.0 2026-09-08

Embed this score

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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/spaceship-mcp/badge.svg)](https://mcptrustchecker.com/registry/spaceship-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/spaceship-mcp"><img src="https://mcptrustchecker.com/registry/spaceship-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/spaceship-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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

Use the free API → How scoring works

Other implementations of Spaceship 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Other