Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SpaceNexus space data

REMOTE · SPACENEXUS.US · SCANNED OCT 5

Read-only space industry data: launches, slips, funding, companies, space weather, Moon race, jobs.

Available components

75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2434 tokens (~173/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the SpaceNexus space data MCP server?

SpaceNexus space data is a hosted endpoint at https://spacenexus.us/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · spacenexus.us

# add to Claude Code
claude mcp add --transport http us-spacenexus-spacenexus 'https://spacenexus.us/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "us-spacenexus-spacenexus": {
      "url": "https://spacenexus.us/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "us-spacenexus-spacenexus": {
      "type": "http",
      "url": "https://spacenexus.us/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.us-spacenexus-spacenexus]
url = "https://spacenexus.us/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-spacenexus-spacenexus": {
      "type": "remote",
      "url": "https://spacenexus.us/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add us-spacenexus-spacenexus --url 'https://spacenexus.us/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  us-spacenexus-spacenexus:
    url: "https://spacenexus.us/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "us-spacenexus-spacenexus": {
      "Transport": "http",
      "Url": "https://spacenexus.us/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add us-spacenexus-spacenexus -t streamable-http -u 'https://spacenexus.us/api/mcp'
// mcp.json
{
  "mcpServers": {
    "us-spacenexus-spacenexus": {
      "type": "http",
      "url": "https://spacenexus.us/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Sept 26 73

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 8 Oct 2026 · Probed https://spacenexus.us/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=spacenexus.us CN=YE1,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 ECDSA 256 ECDSA-SHA384 61d1f77314fc3bd118de82880e8b5844f52
SANs: spacenexus.us
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of spacenexus.us. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
us. present 59017 8 Verified
spacenexus.us. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spacenexus.us/api/mcp Verified 200
http (plaintext) http://spacenexus.us/api/mcp HTTPS enforced 301 https://spacenexus.us/api/mcp
MCP tools · 14 exposed · ~2,225 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
company_lookup ~128

Public profile facts for a space company: what it does, sector, country, headquarters, founding year, public or private, ticker, funding and last round as shown on its profile (for a listed company the funding figure is the private rounds it raised before listing, and fundingBasis says which rule applies), and its Space Score when it is ranked.

NameTypeReqDescription
limitinteger–How many matching companies to return (1 to 5).
querystringyesCompany name, profile slug or stock ticker, e.g. "Rocket Lab", "rocket-lab" or "RKLB".

No output schema declared.

No examples provided.

dataset_links ~104

Needs a SpaceNexus API key (a free key is enough). The bulk SpaceNexus datasets: for each one its CSV and JSON download links, what it holds, its columns, its licence statement, its DOI when minted and the page that shows it, plus the Promise Ledger CSV. The downloads themselves need no key.

NameTypeReqDescription
datasetstring–One dataset by slug or a word of its title, e.g. "launch-slips" or "funding".

No output schema declared.

No examples provided.

funding_round_history ~267

Needs a SpaceNexus API key on the Professional or Research plan. The full published history of private funding rounds into space companies, not only the last 90 days: date, amount (null when undisclosed or stated only approximately, never estimated), series and round type, pre- and post-money valuation where the source names the basis, lead investor and every listed investor, how the round is evidenced and its source link. Filter by company, investor, stage, dates and amount; page with offset.

NameTypeReqDescription
companystring–Company name or profile slug (substring).
investorstring–Investor name: matches the lead investor or any listed investor (substring).
limitinteger–How many rounds to return (1 to 25).
min_amount_usdnumber–Only rounds with a disclosed amount at or above this, in US dollars.
offsetinteger–Rounds to skip, for paging (0 to 10000).
sincestring–Rounds dated on or after this day (YYYY-MM-DD).
stagestring–Round stage or series label (substring), e.g. "Seed", "Series B".
untilstring–Rounds dated on or before this day (YYYY-MM-DD).

No output schema declared.

No examples provided.

launch_ledger_record ~319

Needs a SpaceNexus API key (a free key is enough). The full Launch Ledger record: every launch date change our ledger holds since recording began, one row per launch per UTC observation day, with the observation fields (live or catch-up, the catch-up reason, Launch Library 2's last-updated time), both dates at their precision and its basis, the size and kind of the move, and whether it counts as a slip. Filter by launch, provider, rocket, observation, kind and day; page with offset. The same rows as the free launch-slips dataset.

NameTypeReqDescription
kindstring–Only this kind of move: slip, pull-in, adjust, firmed, loosened or placeholder.
launchstring–One launch: its name or mission (substring, e.g. "Starship Flight 14") or its Launch Library 2 id.
limitinteger–How many rows to return (1 to 25).
observationstring–live: changes our sync saw when they happened; catch-up: changes it only caught up with late; all: both.
offsetinteger–Rows to skip, for paging (0 to 10000).
providerstring–Only launches by this provider (substring or common short name, e.g. "ULA", "CASC").
rocketstring–Only launches of this rocket (substring).
sincestring–Only changes observed on or after this UTC day (YYYY-MM-DD).

No output schema declared.

No examples provided.

launch_on_time_record ~123

How often launches fly on time: the share of flown launches that lifted off within 1 day and within 7 days of the first firm date on record, with mean and median delay, grouped by provider, vehicle or launch site.

NameTypeReqDescription
group_bystring–Group the on-time record by launch provider, vehicle or launch site.
limitinteger–How many groups to return (1 to 25).
namestring–Only groups whose name contains this text, e.g. "SpaceX" or "Falcon 9".

No output schema declared.

No examples provided.

launch_slips ~209

Recent launch date changes as the SpaceNexus slip ledger recorded them (old date, new date, size of the move, kind of move), with totals since recording began and the provider scorecard once the ledger is large enough. Each change carries observation: live (our sync saw it when it happened) or catch-up (our sync only caught up late, so observedAt is when we saw it, not when it changed). Caught-up changes are returned apart in caughtUpChanges and never counted in the summary figures.

NameTypeReqDescription
limitinteger–How many recent date changes to return (1 to 25).
providerstring–Only moves by this provider: a name or common short name (ULA, ISRO, CASC).
real_moves_onlyboolean–Leave out placeholder moves (a "NET 2026" style date firming or rolling); keep slips, pull-ins and adjustments.
rocketstring–Only moves of this rocket (substring).

No output schema declared.

No examples provided.

moon_race_status ~59

The US vs China Moon race tracker: milestones demonstrated on both 8-rung ladders (crewed landing and sustained presence), who leads each, the projection call with its date bands, official targets and the next uncrewed landing attempt.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

next_launches ~297

Upcoming orbital launches from the SpaceNexus manifest (the next 50 scheduled), filterable by provider, rocket, launch site and country. Each launch has its NET date and precision, status, the date changes our ledger recorded, and its page URL. realSlips and otherDateMoves count only changes our sync saw when they happened; caughtUpDateMoves counts changes it only caught up with late (made earlier, on a day we do not know), which are never counted as slips.

NameTypeReqDescription
countrystring–Country of the launch site, by name or code, e.g. "United States", "China", "France" (Kourou), "NZL".
include_recent_outcomesboolean–Also return launches flown in the last 30 days with their outcome.
limitinteger–How many launches to return (1 to 20).
providerstring–Launch provider: a name or common short name, e.g. "SpaceX", "ULA", "ISRO", "CASC", "Rocket Lab".
rocketstring–Rocket, matched as a substring, e.g. "Falcon 9", "Starship", "Long March".
sitestring–Launch site: a spaceport name or slug ("Cape Canaveral" includes Kennedy, "vandenberg", "Starbase", "Andoya") or any pad name.

No output schema declared.

No examples provided.

promise_ledger_entries ~209

Needs a SpaceNexus API key (a free key is enough). Entries from the SpaceNexus Promise Ledger: dated public commitments about spaceflight by agencies, companies and executives, each with the verbatim quote, who said it and when, the deadline as stated and normalised, the status shown today, the outcome and its source, and every later revision. Filter by party, status, claim type or words; page with offset.

NameTypeReqDescription
claim_typestring–Only this kind of claim.
limitinteger–How many entries to return (1 to 25).
offsetinteger–Entries to skip, for paging (0 to 10000).
partystring–An organisation or a person: name or slug, e.g. "SpaceX", "NASA", "elon-musk".
querystring–Words to find in the claim, quote or context.
statusstring–Only entries shown with this status today.

No output schema declared.

No examples provided.

recent_funding_rounds ~149

Closed private funding rounds into space companies in the last 90 days, newest first, with amount (null when undisclosed, never estimated), stage, investors, how the round is evidenced and its source link.

NameTypeReqDescription
companystring–Company name, matched as a substring.
daysinteger–Look-back window in days (1 to 90).
limitinteger–How many rounds to return (1 to 25).
min_amount_usdnumber–Only rounds with a disclosed amount at or above this, in US dollars.
stagestring–Round stage, matched as a substring, e.g. "Seed", "Series B".

No output schema declared.

No examples provided.

search_site ~95

Search spacenexus.us: companies, rockets, launches, launch sites, guides, charts, Moon missions, funding rounds and analysis. Returns titles, one-line descriptions and the canonical URL of each page.

NameTypeReqDescription
limitinteger–How many results to return (1 to 10).
querystringyesWhat to look for on spacenexus.us: a company, rocket, launch, guide, chart or topic.

No output schema declared.

No examples provided.

space_jobs_count ~79

How many open roles the SpaceNexus jobs board lists right now (mirrored daily from employers' careers pages), how many employers are hiring, how many roles are new this week or remote, and optionally one employer's open roles.

NameTypeReqDescription
companystring–Employer name; returns that employer's open roles on the board when we track it.

No output schema declared.

No examples provided.

space_score_history ~124

Needs a SpaceNexus API key whose owner has SpaceNexus Research (the Space Score history is a Research product). One company's daily Space Score readings for up to 365 days: score, rank, the change from the previous reading, large moves flagged, and why a reading moved where the stored inputs can say. The current score stays free in company_lookup.

NameTypeReqDescription
companystringyesCompany name or profile slug, e.g. "Rocket Lab" or "rocket-lab".
daysinteger–Look-back window in days (1 to 365).

No output schema declared.

No examples provided.

space_weather_now ~63

Current geomagnetic Kp and NOAA G-scale, solar wind speed, density and Bz, the NOAA 3-day flare outlook and flares in the last 14 days, with a plain-language read for satellite operators. NOAA SWPC and NASA DONKI data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the SpaceNexus space data MCP server?

SpaceNexus space data is an MCP server listed in the public MCP registry as us.spacenexus/spacenexus. Read-only space industry data: launches, slips, funding, companies, space weather, Moon race, jobs. This page covers its hosted endpoint (https://spacenexus.us/api/mcp).

Is the SpaceNexus space data MCP server safe to use?

SpaceNexus space data scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SpaceNexus space data MCP server expose?

SpaceNexus space data exposes 14 tools: next_launches, launch_slips, launch_on_time_record, recent_funding_rounds, company_lookup, and 9 more. Their descriptions and schemas cost roughly 2,225 tokens of context every time the server is loaded.

Does the SpaceNexus space data MCP server require authentication?

No. We connected to SpaceNexus space data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SpaceNexus space data MCP server still maintained?

SpaceNexus space data is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.