mcpField
M
mrd

mrd

Remote
newspacemarket.comScience & Education1Updated 6w ago

About mrd

mrd provides traceable, machine-readable spacecraft component specifications for engineers and AI assistants. It supports requirements-based matching, datasheet analysis, and bus planning while identifying missing data and source pages.

Key features

  1. 01Match components to engineering requirements
  2. 02View category specs and datasheet digests
  3. 03Total mass and power; check bus voltage
  4. 04Search datasheet facts and excerpts
  5. 05Identify product and category data gaps
  6. 06Plan spacecraft bus configurations

Use cases

  1. 01Filter components by mass, voltage, and other constraints
  2. 02Compare candidates and inspect unmet requirements
  3. 03Estimate stack mass and steady-state power
  4. 04Find specification sources or missing fields

MCP support

It provides eight tools for MCP clients to query component specifications, datasheets, and bus designs. Clients can connect to the hosted endpoint or use a stdio bridge for local editors.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://newspacemarket.com/mrd-connect/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@newspacemarket/mrd-mcp1.2.0

Tools

14
ParameterTypeRequiredDescription
subtypestringNooptional subtype slug, e.g. cmg, heatpipe, sequencer
categorystringYescategory slug, e.g. reaction-wheels, deployers, thermal

Details

From the project README

MRD — machine-readable datasheets for spacecraft components

MCP Registry Smithery Data licence Code licence

Typed, datasheet-sourced specifications for 2,500+ flight hardware products across 24 categories — reaction wheels, star trackers, propulsion, radios, antennas, structures, ground stations and more — with 19,900+ values that each cite the datasheet page they came from. Underneath sits the datasheet layer itself: 26,000+ facts read from 800+ datasheets, each anchored to a quoted page, and the full text of 1,600+ datasheets indexed for questions.

Built for software and AI assistants, not only for reading. Ask in plain language, filter by engineering requirements, or download the whole thing.

"Find a reaction wheel over 0.2 N·m·s that runs on a 12 V bus, under 2 kg"

A  meets every requirement          VRW-B-02 · Vectronic · 0.2 N·m·s · 9–36 V · 1000 g
B  fails a named requirement        RW-0.06 · momentum 0.06 N·m·s — need ≥ 0.2
C  could fit, data not published    NanoTorque GSW-600 · missing: supply voltage

Three rules make the data usable by a machine:

  • Nothing is guessed. A missing property means the vendor does not publish it, and the item is reported as "data missing" rather than silently dropped or filled with a typical value.
  • Conditions are kept apart. Idle, steady-state and peak power are separate records with their measurement condition attached — never averaged into one number.
  • Every value is traceable. Source file and page, plus a confidence level: L0 machine-extracted, L1 verified by a human against the vendor datasheet.

Use it from an AI assistant (MCP)

Hosted — no install. Add this as a custom connector in Claude, ChatGPT (developer mode) or any MCP client:

https://newspacemarket.com/mrd-connect/mcp

Local — for editors that speak stdio (Cursor, Windsurf, VS Code, Claude Desktop). Add to your MCP config:

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

The package is a thin bridge: it speaks stdio to your editor and forwards to the hosted endpoint, so new tools appear without upgrading anything.

Eight tools arrive in the assistant:

toolwhat it does
match_componentsreverse search — requirements in, candidates grouped A / B / C with per-parameter verdicts; optional price ceiling and export-control filter
get_component_specsthe full typed layer of one category, for your own comparison or trade study
build_budgetmass and steady-state power of a stack, with bus-voltage checks and an honest list of what could not be counted
get_datasheet_digestfacts machine-read from one product's datasheet, by section (electrical, interfaces, mechanical, thermal, qualification, commercial…), each with page and verbatim quote
search_datasheet_factsone fact key across a whole category — connector, protocol, TID, flight heritage, lead time, price — one row per product with page and quote
ask_datasheetask a datasheet a question and get the closest excerpts with page numbers, or scan every datasheet of a category for an exact term
design_stacka whole spacecraft bus from a plain-language task; pass fixed product ids to lock parts you have already chosen
find_data_gapswhat is missing for a product, company or category and where to get it: already in the digest, in the datasheet text, or only from the vendor

Where it is listed

  • Official MCP Registry — io.github.newspacemarket-com/mrd
  • Smithery — info-zrja/newspace-mrd, one-click install into Claude, Cursor, VS Code and other clients
  • Dataset mirror — Hugging Face

Use it from code

No authentication for reading. An optional free key raises rate limits five-fold — request one at /mrd-connect/.

curl "https://newspacemarket.com/mrd-connect/match?category=star-trackers&accuracy_max=10&bus_v=12"

The same four datasheet-layer calls are plain REST as well: /mrd-connect/digest?product_id=…, /mrd-connect/facts?category=…&key=…, /mrd-connect/datasheet?product_id=…&q=…, /mrd-connect/gaps?category=….

OpenAPI 3.1: openapi.json, served live at https://newspacemarket.com/mrd-connect/openapi.json. Import it as a ChatGPT Custom GPT Action, a LangChain / CrewAI / n8n toolkit, or convert it to Gemini function declarations.

Download the data

data/ holds a dated snapshot, regenerated as the layer grows:

filecontents
mrd-full.jsoneverything — products, values, property dictionary
mrd-values.csvone row per value: product, property, number, unit, bound, condition, source, confidence
mrd-products.csvone row per product: name, manufacturer, category, URL
mrd-properties.csvthe property dictionary — what each key means and its canonical unit

Live data is always newer than the snapshot; use get_component_specs or /mrd-connect/specs?category=… when freshness matters.

How the data is built

Values are extracted from vendor datasheets (text and, for scanned documents, page images), from vendor product pages, and from product descriptions — the source of every record says which. Units are converted by code, not by a model: kg to g, dBm to W, psi to bar, tf to mN. A validation pass rejects a figure whose unit does not match the property, and an outlier scan flags values that sit far from the category median for human review.

Coverage is not exhaustive. Where a vendor publishes nothing machine-readable, the product simply is not here — and where a required field is missing, the API says so by name instead of guessing.

Licence

  • Code (the MCP bridge and examples): MIT — see LICENSE.
  • Data in data/: CC BY 4.0, attribution "NewSpace Market" — see data/LICENSE-DATA.

Specifications are extracted from publicly published vendor materials and are provided as-is. Verify against the vendor datasheet before committing to a design.

Links

Are you a vendor whose products are listed? Completing the missing fields takes minutes and is free — write to us from your company domain and we will send a direct link.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.