Is Spaceship Mcp safe to use?

Spaceship Mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install Spaceship Mcp?

Spaceship Mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with Spaceship Mcp?

Spaceship Mcp is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.

Is Spaceship Mcp actively maintained?

Spaceship Mcp is recently maintained — last commit was 36 days ago. It has 8 GitHub stars.

45CNo CVEsmaintainedMIT

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/spaceship-mcp)](https://mcppedia.org/s/spaceship-mcp)

✓

Is it safe?

No known CVEs for npm. 8 previously resolved.

No authentication — any process on your machine can connect.

MIT. View license →

✓

Is it maintained?

Last commit 36 days ago. 8 stars. 12,072,835 weekly downloads.

Will it work with my client?

Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

MCPpedia Score

Click each category to see evidence

45C

Last scored 23h ago

How we score →

Security

22/30

No open vulnerabilities. 8 fixed CVEs.

✓

Known CVEs — No known CVEs for npmcheck OSV.dev

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

✓

Tool stability — Tool definitions stable

○

Dependency health — found on deps.dev

✓

License — License: MIT

○

Authentication — No authentication required

○

Repository — active repo

Advisories (0 open, 8 fixed)

lowCVSS 3.1CVE-2022-29244Fixed

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0Published Jun 2, 2022source \u2192

lowCVSS 3CVE-2018-7408Fixed

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1Published May 13, 2022source \u2192

CVEs checked daily via OSV.dev. Score algorithm is open source.

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

MCP Security Weekly

Get CVE alerts and security updates for Spaceship Mcp and similar servers.

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

lowCVSS 3.1CVE-2020-15095Fixed

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6Published Jul 7, 2020source \u2192

lowCVSS 3.1CVE-2019-16777Fixed

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4Published Dec 13, 2019source \u2192

lowCVSS 3.1CVE-2019-16776Fixed

npm symlink reference outside of node_modules

Versions of the npm CLI prior to 6.13.3 are vulnerable to a symlink reference outside of node_modules. It is possible for packages to create symlinks to files outside of the`node_modules` folder through the `bin` field upon installation. A properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user’s system when the package is installed. Only files accessible by the user running the `npm install` are affected.

Affected: >= 0Fixed in 6.13.3Published Dec 13, 2019source \u2192

lowCVSS 3.1CVE-2019-16775Fixed

Arbitrary File Write in npm

Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to create files on a user's system when the package is installed. It is only possible to affect files that the user running `npm install` has access to and it is not possible to over write files that already exist on disk

Affected: >= 0Fixed in 6.13.3Published Dec 13, 2019source \u2192

infoCVE-2016-3956Fixed

npm Token Leak in npm

Affected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry. An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token. This compromised token could be used to do anything that the user could do, including

Affected: >= 0Fixed in 2.15.1Published Jul 31, 2018source \u2192

Spaceship MCP Server

An MCP (Model Context Protocol) server for the Spaceship API, providing easy-to-use tools for managing DNS records. Features specialized tools for common record types (A, AAAA, CNAME, MX, SRV, TXT) with explicit parameters, plus generic tools for advanced use cases.

⚠️ Warning: use with care

This MCP server gives AI agents direct control over your DNS records. This can be helpful but also dangerous because:

Domain takeover risk: Incorrect DNS changes could redirect your domain to malicious sites
Service disruption: Wrong DNS records can make your websites and services inaccessible
Permanent consequences: Some DNS changes can have lasting effects on your domain's reputation
Unintended modifications: AI agents may make DNS changes you didn't expect or want

Recommendations:

Review AI-suggested DNS changes before confirming them
Keep backups of your current DNS configuration
Monitor your domains closely when using this server
Avoid using it with an AI agent that may also be accessing untrusted content

Status

I use this myself for my own projects.

Limited testing: As far as I know it is not in widespread use
No automated tests: There are currently no unit tests or integration tests
Use at your own risk: Suitable for experimentation but not recommended for critical systems

Contributions, bug reports, and feedback are welcome to help improve the project's stability and reliability.

Features

Core Operations

List DNS Records: Retrieve all DNS records for a domain
Delete DNS Records: Remove DNS records from a domain

Specialized Record Creation Tools

Type-specific tools with explicit parameters for easy, error-free DNS management:

A Records: Create IPv4 address records
AAAA Records: Create IPv6 address records
CNAME Records: Create canonical name aliases
MX Records: Create mail exchange records with priority and exchange parameters
SRV Records: Create service locator records with priority, weight, port, and target
TXT Records: Create text records for SPF, DKIM, DMARC, verification, etc.

Generic Tools

Create/Update DNS Records: Generic tools supporting all DNS record types for advanced use cases

Installation

Prerequisites

Node.js ≥ 18
An MCP-compatible client (e.g. Claude Desktop, Cursor, Continue)
Spaceship API credentials (see Configuration section below)

Install the server

Clone the repository and build:

git clone https://github.com/mattcollins/spaceship-mcp.git
cd spaceship-mcp
npm install
npm run build

Configure your MCP client

Add the server to your MCP client configuration.

Example (Claude Desktop)

Edit claude_desktop_config.json:

{
  "mcpServers": {
    "spaceship": {
      "command": "node",
      "args": ["/absolute/path/to/spaceship-mcp/dist/index.js"],
      "env": {
        "SPACESHIP_API_KEY": "your_api_key",
        "SPACESHIP_API_SECRET": "your_api_secret"
      }
    }
  }
}

Replace /absolute/path/to/spaceship-mcp with the actual path where you cloned the repository.

Restart the client after saving the file.

Verify the installation

After restarting your client, confirm the server is running:

The server appears in the client's MCP/server list
No errors appear in the client logs
Tools exposed by the server (like list_dns_records) are available to the model

To check for startup errors, you can run the server manually:

npm start

Configuration

Environment Variables

| Variable | Description | Required | | ----------------------- | ---------------------------------- | -------- | | SPACESHIP_API_KEY | Your Spaceship API key | Yes | | SPACESHIP_API_SECRET | Your Spaceship API secret | Yes |

Get your API credentials from the [Spaceship API Manager](https://www.spaceshi

... View full README on GitHub

Spaceship Mcp

Quick Install

Should you use this server?

Test This Server

Score Breakdown

MCPpedia Score

Security

Advisories (0 open, 8 fixed)

Reviews

Frequently Asked Questions

Similar servers

Sequential Thinking MCP Server

Arxiv Mcp Server

Gemini Cli

Python Sdk

Discussion