space-standards-mcp
Related Servers
Alternatives to space-standards-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables retrieval and comparison of automotive regulations and standards, plus question answering where every answer must carry standard number, clause number, and original excerpt, with unsupported conclusions flagged for review. Java backends and Feishu can call it directly over MCP.-
- AlicenseNot gradedqualityAmaintenanceEnables evidence-first, read-only analysis of IETF RFCs with pinned content-addressed snapshots, byte-exact citations, and RFC 2119/8174 requirement extraction. Provides tools, resources, and prompts for resolving, reading, searching, comparing, and verifying RFC content with provenance.2 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceRuns a local, file-based toolkit of 100 systems engineering skills that lets an AI assistant clean and map requirements, review specifications against ECSS, derive sub-requirements, check interfaces and budgets, and build verification and compliance matrices. It works on documents in a user-chosen local folder without sending customer data to a remote service or requiring an account or API key.25 PyPI12MIT
- FlicenseNot gradedqualityCmaintenanceEnables document indexing and question answering with Retrieval-Augmented Generation, providing cited answers from user-supplied documents.-
- AlicenseNot gradedqualityBmaintenanceSpacecraft component specifications read from vendor datasheets (2,500+ products, 24 categories): search by engineering requirements, compare, budget mass and power, read datasheet digests and facts, find data gaps, and assemble a bus around parts you lock. Every value cites its datasheet page; missing data is named, never guessed.51 npm1MIT
- FlicenseAqualityBmaintenanceLocal-first, read-only MCP server for retrieving and searching authorised CCSDS and ECSS standards, enabling citation-rich passage-level search and document access.3-
TDQS
Scored across 7 tools
Each tool targets a distinct retrieval unit (document list, single requirement, outline, table, references, cross-doc comparison), so selection is mostly unambiguous. The only mild overlap is between search_requirements and compare_topic, but the latter's multi-doc side-by-side framing and topic-only query make the boundary clear.
All names follow a consistent snake_case verb_noun pattern (list_documents, get_requirement, get_table, search_requirements, compare_topic). No mixed conventions or vague verbs.
Seven tools is well-scoped for a read-only standards corpus, with each tool earning its place by covering a different access granularity (list, search, outline, requirement, table, references, comparison). No redundancy or padding.
The surface covers the main read paths for a standards domain: discovery, search, drill-down to requirements/tables, references, and cross-standard comparison. Minor gap: no tool to load documents (only referenced via corpus.yaml), and no bulk export, but these are workable around.