# Space Standards (pypi · space-standards-mcp)

Cited, requirement-level Q&A over ECSS and NASA standards you supply (bring your own documents)

- Trust score: 85/100 (high trust)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `space-standards-mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/manojknaikade-space-standards-mcp/space-standards-mcp.md), [page](https://verifymcp.io/servers/manojknaikade-space-standards-mcp/space-standards-mcp)

## Channel facts

- Registry: `pypi`
- Package: `space-standards-mcp`
- Version: `0.2.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 39 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to manojknaikade/space-standards-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 19 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1650 tokens (~235/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Space Standards MCP server?

Space Standards runs locally as a PyPI package, launched with uvx space-standards-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add manojknaikade-space-standards-mcp -- uvx space-standards-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "manojknaikade-space-standards-mcp": {
      "command": "uvx",
      "args": [
        "space-standards-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "manojknaikade-space-standards-mcp": {
      "command": "uvx",
      "args": [
        "space-standards-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add manojknaikade-space-standards-mcp -- uvx space-standards-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "manojknaikade-space-standards-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "space-standards-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add manojknaikade-space-standards-mcp --command uvx --arg space-standards-mcp
```

### Hermes

```yaml
mcp_servers:
  manojknaikade-space-standards-mcp:
    command: "uvx"
    args: ["space-standards-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "manojknaikade-space-standards-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "space-standards-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add manojknaikade-space-standards-mcp -t stdio -c uvx -a space-standards-mcp
```

### Other

```json
{
  "mcpServers": {
    "manojknaikade-space-standards-mcp": {
      "command": "uvx",
      "args": [
        "space-standards-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 69, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 68, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-30 (score 83, +1)

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

### 2026-10-29 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 67, +1)

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

### 2026-10-27 (score 66, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (7)

### `list_documents` (~264 tokens)

List the standards currently loaded: issue, title, family (ECSS / NASA), doc_type (standard, handbook, ...),
discipline, record counts and parse `tier` ("verified": hand-checked against the source; "checked": passes the
automatic parse health checks; "unchecked": parsed automatically — for both, check numbers against the source
page before relying on them).

Filters (optional, case-insensitive): family "ECSS" or "NASA"; doc_type e.g. "handbook"; discipline as a
code ("E-32", "Q-70", "NASA-5000") or a name ("structures"); query: words in the doc ID or title.
include_not_loaded: also list standards in the user's documents folder that are not loaded (`loaded: false`).
Their text is not available: never answer from them, but you may name one as the standard that would cover
a question. Returns {"count", "documents"} (at most `limit`, plus "truncated" when more match).

Input parameters:

- `discipline` (string)
- `doc_type` (string)
- `family` (string)
- `include_not_loaded` (boolean)
- `limit` (integer)
- `query` (string)

### `get_requirement` (~208 tokens)

Get the exact text of one requirement.

doc_id: e.g. "ECSS-Q-ST-80C" or "ECSS-Q-ST-80" or "NPR 7150.2".
req_id: ECSS clause + letter, e.g. "5.2.1a" (DRD content: "A.2.1<5.2>a"); NASA tag, e.g. "FSR 24",
or an FCR item, e.g. "FCR 11 / 7.2.1.c"; untagged NASA standards: section + item, e.g. "4.2a", "4.3(1)",
or the n-th "shall" paragraph of a section, e.g. "4.4 req 1". Records carry a `kind`: requirement, recommendation,
permission, guidance or deleted — say which when answering.

Input parameters:

- `doc_id` (string, required)
- `req_id` (string, required)

### `search_requirements` (~400 tokens)

Search across loaded requirements (BM25; hybrid with embeddings when the server enables it).
Optionally restrict to one document.

query: REQUIRED search words, never empty, e.g. "ultimate factor of safety metallic structure" or
"fracture control NASA-STD-5019". A call without search words returns no results.

Returns {"results": [...]} plus, when relevant, "not_loaded", "elsewhere" and "notes".
Without doc_id, standards named in the query (e.g. "NASA-STD-5001B", "ECSS-E-ST-32-01") restrict
the search to them. `not_loaded` lists named standards that are not loaded: never answer from
them. It is split into `in_documents_folder` (present in the user's documents folder but not loaded,
with issue and status: say so, and that they can be loaded through corpus.yaml) and
\`not_in_documents_folder` (the user does not have them). `elsewhere` holds stronger hits from other loaded documents when the named document
matches weakly — it may not cover the topic. Table rows are searched too: a hit found through a
table carries `matched_table_row` (table citation, row labels, cells) — take the numbers from
there or from get_table, and cite both the requirement and the table. Records and rows carry `tier`
(verified, checked, unchecked) and `page`; rows from tables below `verified` carry `check`: repeat it
("check against the source, page N") next to any number taken from them. Each hit may carry
\`neighbours`: the records next to it in the same clause (a requirement is often split over sibling
letters). They are full records with citations; read them before concluding a clause is not covered.

Input parameters:

- `doc_id`
- `limit` (integer)
- `query` (string, required)

### `get_table` (~212 tokens)

Get a table (e.g. factors of safety) as structured rows, verbatim from the source.

doc_id: e.g. "ECSS-E-ST-32-10C" or "NASA-STD-5001B". table_id: e.g. "Table 4-3" or "4-3".
Each row has row labels and value cells (text as printed, parsed value, footnote markers).
Quote the cell text and its footnotes; 'spans_rows' marks a value printed once in a merged
cell that covers several rows. The table and each row carry `tier` and `page`; below `verified` they also
carry `check` ("check against the source, page N"): give every number from such a table with that flag
(an answer that does not repeat it fails the citation check). Omit table_id (empty string) to list the tables of a document.

Input parameters:

- `doc_id` (string, required)
- `table_id` (string)

### `get_references` (~41 tokens)

List the standards and clauses that a requirement (or its notes) refers to.

Input parameters:

- `doc_id` (string, required)
- `req_id` (string, required)

### `compare_topic` (~222 tokens)

Side-by-side search of one topic in several standards, e.g. ECSS vs NASA on factors of safety.

topic: the subject only, e.g. "ultimate design factor metallic structure" (no standard names).
doc_ids: the standards to compare, e.g. ["ECSS-E-ST-32-10", "NASA-STD-5001"]; omit for all loaded.
Returns one section per document, grouped by family (ECSS, NASA), with its top hits and the
table rows they matched. Requested or named standards that are not loaded are listed as in
search_requirements (`not_loaded`, `in_documents_folder`, `not_in_documents_folder`). `coverage: "weak"` marks a document whose best hit is far below the
best hit elsewhere: it may not treat the topic — say so rather than force an equivalence.
Coverage is judged on keyword matches: read the hits, and use get_requirement / get_table before comparing.

Input parameters:

- `doc_ids`
- `limit` (integer)
- `topic` (string, required)

### `get_section_outline` (~157 tokens)

Table of contents of one standard: clause numbers, titles and how many records (by kind) each holds.

doc_id: e.g. "ECSS-E-ST-32-01C" or "NASA-STD-5019A". clause: e.g. "7.2" to list that section and its
subsections, plus the record IDs placed directly in it and the tables in it; omit for the whole document.
depth: how many heading levels to list below the starting point (default 2).
The outline has no requirement text: use get_requirement / get_table for anything you quote or cite.

Input parameters:

- `clause` (string)
- `depth` (integer)
- `doc_id` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/manojknaikade-space-standards-mcp/space-standards-mcp#diagnostics

## Score history

- 2026-11-04: 85
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 84
- 2026-10-31: 68
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 81
- 2026-10-25: 65
- 2026-10-24: 80
- 2026-10-23: 64
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 61
- 2026-10-19: 76
- 2026-10-18: 61
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 61

## Common questions

### What is the Space Standards MCP server?

Space Standards is an MCP server listed in the public MCP registry as io.github.manojknaikade/space-standards-mcp. Cited, requirement-level Q&A over ECSS and NASA standards you supply (bring your own documents). This page covers its PyPI package (space-standards-mcp).

### Is the Space Standards MCP server safe to use?

Space Standards scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Space Standards MCP server expose?

Space Standards exposes 7 tools: list_documents, get_requirement, search_requirements, get_table, get_references, and 2 more. Their descriptions and schemas cost roughly 1,504 tokens of context every time the server is loaded.

### Is the Space Standards MCP server still maintained?

Space Standards is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Space Standards MCP server under?

Space Standards declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/space-standards-mcp/
- Socket report: https://socket.dev/pypi/package/space-standards-mcp
- Repository: https://github.com/manojknaikade/space-standards-mcp
- Changelog RSS feed: https://verifymcp.io/servers/manojknaikade-space-standards-mcp/space-standards-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/manojknaikade-space-standards-mcp/space-standards-mcp.json
- HTML version of this page: https://verifymcp.io/servers/manojknaikade-space-standards-mcp/space-standards-mcp