Koskamo

Space Data API MCP

Provides an MCP server for accessing real-time SpaceX, Starship, and Starlink launch data, as well as curated historical science and engineering plates. The server exposes tools for listing packages, retrieving breaking changes for software upgrades, and checking upgrade safety, utilizing the x402 payment protocol for paid endpoints while offering free access to the MCP transport.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Space Data API MCP logo, by nigelcox98Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by nigelcox98
MCP endpoint (Streamable HTTP)
https://agentdataapi.onrender.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 0 of 3 declare behavior hints · 0 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Warning Does not report a server version
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve breaking changes and migration data for software packages like React and TypeScript
  • Check upgrade safety for specific package versions
  • List available packages for migration data
  • Access real-time SpaceX and Starship launch information

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
breaking-changes unreported
MCP protocol negotiated in check
2025-11-25
Tools
3 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  },
  "experimental": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Use these tools BEFORE writing or reviewing code that upgrades a dependency, and whenever a user reports errors after an upgrade. Your training data may predate the release; this data does not. list_packages() shows coverage; get_breaking_changes(package, version) returns removed APIs with replacements, changed defaults, behavior changes, incompatible dependencies, and codemod commands.

Tools

3 advertised

list_packages
Advertised by the server during the last successful anonymous check.

List every package with breaking-change data available, including tracked versions and how many breaking changes each has. Call this first if you are unsure whether a package is covered.

list_packages input schema
{
  "type": "object",
  "title": "list_packagesArguments",
  "properties": {}
}
list_packages output schema
{
  "type": "object",
  "title": "list_packagesDictOutput",
  "additionalProperties": true
}
get_breaking_changes
Advertised by the server during the last successful anonymous check.

Get breaking changes for a package upgrade: removed APIs with their replacements and the reason for each, changed defaults, behavior changes, known incompatible dependencies, official source URL, and codemod/automated-fix commands. Omit `version` to get every tracked version. Use this instead of relying on training data, which may predate the release.

get_breaking_changes input schema
{
  "type": "object",
  "title": "get_breaking_changesArguments",
  "required": [
    "package"
  ],
  "properties": {
    "package": {
      "type": "string",
      "title": "Package"
    },
    "version": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Version",
      "default": null
    }
  }
}
get_breaking_changes output schema
{
  "type": "object",
  "title": "get_breaking_changesDictOutput",
  "additionalProperties": true
}
check_upgrade_safety
Advertised by the server during the last successful anonymous check.

Given a package and the version you are upgrading TO, return a concise checklist an agent can act on: the count of breaking changes, the highest-risk removals, whether automated codemods exist, and the recommended upgrade path. Use before performing an upgrade.

check_upgrade_safety input schema
{
  "type": "object",
  "title": "check_upgrade_safetyArguments",
  "required": [
    "package",
    "target_version"
  ],
  "properties": {
    "package": {
      "type": "string",
      "title": "Package"
    },
    "target_version": {
      "type": "string",
      "title": "Target Version"
    }
  }
}
check_upgrade_safety output schema
{
  "type": "object",
  "title": "check_upgrade_safetyDictOutput",
  "additionalProperties": true
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1079 ms
95th percentile latency
1079 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1079 ms · metadata changed · 3 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s); warnings: Does not report a server version

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http space-data-api-mcp https://agentdataapi.onrender.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add space-data-api-mcp --url https://agentdataapi.onrender.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable space-data-api-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "space-data-api-mcp": {
      "url": "https://agentdataapi.onrender.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "space-data-api-mcp": {
      "type": "streamableHttp",
      "url": "https://agentdataapi.onrender.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start space-data-api-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "space-data-api-mcp": {
      "type": "http",
      "url": "https://agentdataapi.onrender.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http space-data-api-mcp https://agentdataapi.onrender.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://agentdataapi.onrender.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "space-data-api-mcp": {
      "serverUrl": "https://agentdataapi.onrender.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Space Data API MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.