# mrd [Health: Active]

**Category:** 🚀 Aerospace & Astrodynamics  
**Repository:** https://github.com/newspacemarket-com/mrd  
**GitHub Stars:** 1  
**npm Downloads (last month):** 124  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mrd

## Description
Spacecraft component specs from vendor datasheets: search, dumps, budgets

## Tools
Capabilities this server exposes over MCP:

- **explain_properties** — What every property of a product category means: definition, how it is measured and what goes into the measurement condition, how to use it when selecting, what it is commonly confused with, typical range and related properties. Call this before interpreting specs of an unfamiliar category.
- **match_components** — Reverse search over a typed spec layer: pass a category and engineering requirements, get every catalogued item grouped as A (meets all stated requirements), B (fails a named requirement, both figures quoted) or C (could fit, data missing). Verdicts cite the datasheet page. Omit parameters you do not care about. Categories: reaction-wheels, star-trackers, obc-computers, batteries, radios, solar-panels, propulsion, sun-sensors, magnetometers, magnetorquers, imus-gyros, gnss-receivers, eps, deployers, thermal, antennas, sdr-modems, cameras, structures, platforms, ground-stations, sadm, tanks-valves, separation-systems, pointing-mechanisms, test-facilities (environmental test labs — items are companies: test, shaker_min_kn, tvac_min_m, specimen_min_kg, emc_min_m). The answer is compact: group A in full (up to 25), groups B and C — the first 10 with the reason, plus counts and the fields most often unpublished in C; page with group and offset.
- **find_alternatives** — Alternatives / second sources / replacements for ONE product: requirements are derived from its own published values (key fields of its class — higher-is-better at least 80 %, lower-is-better at most 120 %, same interface, band or type) and its class is searched without it. Returns the derived requirements, fields not compared, and groups A (meets all), B (fails one), C (data missing). Use when a part has a long lead time, is discontinued or export-restricted. Equal figures do not make a drop-in replacement — interfaces must be confirmed with the manufacturer.
- **selection_guide** — How to choose a product of one category, from the catalogue data only: the decisive parameters with real ranges (middle half and full range), which side is better, how many products publish each, what to ask the vendor, and ready match queries. category = "cubesat" gives the list of subsystems a CubeSat is built from with catalogue counts.
- **find_suppliers** — Companies whose PRODUCTS meet engineering requirements in one category — "who makes platforms for GEO", "Chinese companies making star trackers better than 10 arcsec", "suppliers of flight-proven reaction wheels". Pass category, optional country and any requirement parameter of match_components (same names and units). Returns companies with their matching products, and how many more companies may fit because the decisive value is not published.
- **build_budget** — Engineering budget for a component stack: pass product ids (from the other tools) and your bus voltage, get total mass, total steady-state power, per-item data interfaces, voltage-compatibility verdicts and an honest list of what could NOT be counted because the vendor does not publish it. Use it to assemble and sanity-check a subsystem, e.g. 3-4 reaction wheels for an ADCS.
- **get_component_specs** — The typed layer of a category, 10 products per call (page with offset, narrow with ids and keys) — every item with every value (number, canonical unit, bound, measurement condition, datasheet source page, confidence L0/L1) plus the property dictionary grouped by interface port (perf/power/data/mech/thermal/env/supply) — for arbitrary comparison, budgeting or trade studies on your side.
- **get_datasheet_digest** — Facts machine-read from a product datasheet, by section (identity, performance, electrical, interfaces, mechanical, thermal, environmental, qualification, lifetime, options, compliance, commercial). Each fact carries unit, condition, the page and a verbatim quote it was verified against (confidence L0) plus a link into the PDF. Use it for what the typed layer does not hold: connectors, protocols, survival temperature, vibration, radiation, heritage, options, export control, lead time. Pass product_id from match_components or a product name.
- **search_datasheet_facts** — One fact key across a whole category: which products state it in their datasheets and what value — e.g. connector, data_interface, protocol, survival_temperature, tid_tolerance, flight_heritage, trl, export_control, lead_time, price, design_life. One row per product with page and quote. Reports coverage (how many products of the category have a digested datasheet).
- **ask_datasheet** — Ask a product datasheet a question and get the closest excerpts with page numbers (pre-indexed text), or scan ALL datasheets of a category for an exact term (term + category) and get the exact list of products mentioning it with an excerpt each.
- **design_stack** — Assemble a whole spacecraft bus from a plain-language task: the service plans the subsystems, matches every item deterministically against the stated requirements, computes the mass/power budget and writes an evidence-bound rationale. Pass fixed = product ids you have already chosen (from match_components or get_datasheet_digest): they stay in their subsystems, are checked against the requirements (selected.fixed, fixed_verdict, fixed_fails) and the rest is assembled around them. LLM-backed and rate-limited (6/min, 30/h anonymous).
- **find_data_gaps** — What is missing for a product, a company or a category and where to get it: in_digest (already read from the datasheet — value, page), in_datasheet_text (the datasheet mentions it — page, excerpt), not_in_datasheet (ask the vendor), no_datasheet (ask the vendor for a datasheet). For vendors: what to publish; for buyers: what to ask.
- **ask_console** — Plain-language engineering question over the whole platform, answered by platform rules without any external model: selection by requirements, values of a property across a class, companies by capability and country, launch windows, term definitions. Returns a short answer plus data blocks (candidates A/B/C, values, companies, launches). Use when the question does not map cleanly onto one structured tool.
- **check_fit** — Check whether a set of products docks together, by the interface template of each product type: deployer and CubeSat structure form factor and satellite mass, separation system and spacecraft mass, solar panel size and EPS solar input (Voc/Vmp, power), battery and EPS, EPS output rails or the unregulated bus against each unit supply range, EPS charge current against the battery limit, satellite envelope against the deployer envelope for its form factor, on-board computer against unit data interfaces, board stack format, free volume, radio against antenna and ground station (frequency, band, connector, protocol and modulation), antenna against ground station polarization, GNSS receiver signals against the GNSS antenna band, magnetorquer coil current against the driver channel, PPU output power against the electric thruster, array drive against panel power, propulsion propellant against tank media, steady power budget. Verdicts fits / conflict / check / unknown, plus ask_vendor: exactly which values are missing to decide.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mrd": {
    "command": "npx",
    "args": ["-y","@newspacemarket/mrd-mcp"]
  }
}
```

## Documentation

## What the mrd MCP server does

The mrd MCP server gives AI assistants access to typed specifications for spacecraft components across 24 categories, including reaction wheels, star trackers, propulsion, radios, antennas, structures, and ground stations. Its data layer contains more than 19,900 cited values from over 2,500 flight hardware products, alongside 26,000 facts extracted from more than 800 datasheets. Full text from over 1,600 datasheets is indexed for questions.

The mrd MCP server is intended for engineering searches and early trade studies. You can describe requirements in natural language, compare candidates, assemble a spacecraft bus, inspect product facts, or identify information that is not available. Values retain their units, operating conditions, source file, datasheet page, and confidence level. Missing information is reported rather than inferred.

## How it works

The mrd MCP server exposes a hosted MCP endpoint at `https://newspacemarket.com/mrd-connect/mcp`. A local package, `@newspacemarket/mrd-mcp`, provides a stdio interface for editors and forwards requests to that hosted service. The same service also provides REST endpoints and an OpenAPI 3.1 document for integrations such as custom actions or agent toolkits.

Data is extracted from vendor datasheets, scanned document images, vendor product pages, and product descriptions. Unit conversions are performed in code, and validation checks whether a value's unit matches its property. Records include either machine-extracted confidence (`L0`) or human-verified confidence (`L1`).

## Setup and configuration

For a hosted connection, add the MCP URL as a custom connector in an MCP-compatible client. For local stdio clients, add the following entry to the client's MCP configuration:

```json
{
  "mcpServers": {
    "mrd": {
      "command": "npx",
      "args": ["-y", "@newspacemarket/mrd-mcp"]
    }
  }
}
```

No authentication is needed for reading. An optional free key is available through the connection hub and increases rate limits five-fold. The repository also includes Python, JavaScript, and curl examples, while the live OpenAPI document is available at `/mrd-connect/openapi.json`.

## Tools and capabilities

The mrd MCP server provides eight tools:

- `match_components` filters products against engineering requirements and groups results into candidates that pass, fail, or have missing data. It can also apply price and export-control filters.
- `get_component_specs` returns the typed specification layer for a category.
- `build_budget` calculates mass and steady-state power for a component stack, checks bus voltage, and identifies items that could not be counted.
- `get_datasheet_digest` returns product facts by section with page references and quoted source text.
- `search_datasheet_facts` compares one fact key across a category, with a page and quote for each row.
- `ask_datasheet` searches one or all category datasheets for question-related excerpts or exact terms.
- `design_stack` creates a spacecraft bus from a plain-language task and accepts fixed product IDs.
- `find_data_gaps` reports missing information for a product, company, or category and indicates whether it exists in extracted data, indexed text, or only from the vendor.

## Limitations and notes

Coverage is not exhaustive. Products without machine-readable vendor information may be absent, and unpublished properties remain missing. Conditions such as idle, steady-state, and peak power are kept as separate records rather than combined. The repository contains a dated data snapshot, but live queries are newer when freshness matters.

Specifications are provided as-is and should be checked against the vendor datasheet before design commitment. The MCP bridge and examples use the MIT license; the included data uses CC BY 4.0 with attribution to NewSpace Market.

_Full upstream README: https://allmcps.com/mcp/mrd/readme_