io.github.newspacemarket-com/mrd

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Spacecraft component specs from vendor datasheets: search, digests, facts, gaps, budgets, bus design

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "mrd": {
      "url": "https://newspacemarket.com/mrd-connect/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (14)

• 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.

  Parameters:

  • category (required) — string — category slug, e.g. reaction-wheels, deployers, thermal
  • subtype — string — optional subtype slug, e.g. cmg, heatpipe, sequencer

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• match_components read-only

  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.

  Parameters:

  • band — string — radio: frequency band UHF|VHF|S|X|L|C|Ku|Ka
  • test — string — test-facilities: kinds of test the lab must ALL offer, comma-separated — vibration, shock, thermal-vacuum, thermal, emc, radiation, acoustic, magnetic, rf-antenna, mass-properties, outgassing, optical
  • bus_v — number — your power bus voltage, V — the unit must accept it
  • group — string — page through one group only — use with offset from paging.next
  • limit — integer — items of groups B and C to return (default 10, max 50); group A comes in full up to 25
  • media — string — tank/valve: propellant/media, e.g. xenon, hydrazine
  • orbit — string — platforms: orbit the bus is designed for — LEO | SSO | VLEO | MEO | GEO | HEO | lunar | deep space (LEO, SSO and VLEO pass each other)
  • export — string — required export status: ITAR-free | EAR99 | ITAR
  • form_u — number — structures / platforms: CubeSat size, U (exact match)
  • offset — integer — start position inside the group (paging.next.offset of the previous answer)
  • acq_max — number — star trackers: max lost-in-space acquisition time, s
  • arw_max — number — IMU: worst angle random walk, deg per sqrt hour
  • data_if — string — required data interface: CAN, RS-422, RS-485, SpaceWire, I2C, SPI, UART, MIL-STD-1553
  • mpx_min — number — camera: min sensor resolution, Mpx
  • ram_min — number — OBC: min RAM, MB
  • tid_min — number — any category: min radiation tolerance TID, krad
  • category — string — which component class to search — ONE per call; for several classes call once per class (default reaction-wheels)
  • lead_max — number — max lead time, months
  • mass_max — number — max unit mass, grams
  • mass_min — number — min unit mass, grams (rare: "heavier than")
  • material — string — structure: alloy, e.g. Al 7075
  • ttff_max — number — GNSS: worst cold TTFF, s
  • bands_min — number — camera: min spectral bands
  • clock_min — number — OBC: min CPU clock, MHz
  • dv_min_ms — number — platforms / propulsion: min delta-v, m/s
  • emc_min_m — number — test-facilities: min test-article size the EMC / anechoic chamber takes, m
  • gsd_max_m — number — camera: worst ground sample distance, m
  • isp_min_s — number — propulsion: min specific impulse, s
  • link_band — string — platforms: radio band of the bus — UHF | VHF | L | S | X | Ku | Ka | optical
  • power_max — number — max steady-state power, W (peak/regenerative not counted)
  • prop_type — string — propulsion: electric | chemical | cold-gas | water; platforms: electric | chemical | any (the bus carries propulsion)
  • cycles_min — number — battery: min cycle life
  • dish_min_m — number — ground station: min antenna diameter, m
  • gt_min_dbk — number — ground station: min G/T, dB/K
  • life_min_y — number — any category: min design life in orbit, years
  • sunacc_max — number — sun sensor: worst acceptable accuracy, deg
  • torque_min — number — wheels: min torque, mN*m
  • tvac_min_m — number — test-facilities: min usable inner size (diameter or smallest side) of the thermal-vacuum chamber, m
  • update_min — number — star trackers: min update rate, Hz
  • fov_min_deg — number — sun sensors / star trackers / cameras: min field of view, deg
  • mag_res_max — number — magnetometer: worst resolution, nT
  • pos_acc_max — number — GNSS: worst position accuracy, m
  • res_max_deg — number — pointing: max angular resolution, deg
  • shock_max_g — number — separation: max release shock, g
  • slip_min_ch — number — SADM: min slip-ring channels
  • storage_min — number — OBC: min storage, GB
  • txpow_min_w — number — radio: min TX RF power, W
  • accuracy_max — number — star trackers: worst acceptable cross-boresight accuracy, arcsec
  • beam_max_deg — number — antenna: max beamwidth, deg
  • channels_min — number — GNSS: min channels
  • eirp_min_dbw — number — ground station: min EIRP, dBW
  • gain_min_dbi — number — antenna: min gain, dBi
  • meop_min_bar — number — tank/valve: min operating pressure, bar
  • momentum_min — number — wheels: min angular momentum storage, N*m*s
  • outpow_min_w — number — EPS: min total output power, W
  • payvol_min_l — number — platforms: min volume for the payload, litres
  • payvol_min_u — number — platforms: min volume for the payload, U
  • polarization — string — antenna: RHCP|LHCP|linear|circular
  • ptrans_min_w — number — SADM: min power transfer, W
  • range_min_ut — number — magnetometer: min field range, uT
  • sun_excl_max — number — star trackers: max acceptable sun exclusion angle, deg
  • swath_min_km — number — camera: min swath width, km
  • volume_min_l — number — tank/valve: min volume, L
  • bias_max_degh — number — IMU: worst bias instability, deg/h
  • constellation — string — GNSS: required constellation GPS|Galileo|GLONASS|BeiDou
  • flight_proven — boolean — any category: true = only products with stated flight heritage (missions flown, heritage text or TRL 9)
  • paymass_min_g — number — platforms / deployers / separation systems: payload or satellite mass that must fit, grams
  • price_max_eur — number — max indicative price, EUR (few vendors publish it — expect group C)
  • range_min_deg — number — pointing: min travel range, deg
  • rate_min_kbps — number — radio: min data rate, kbps
  • shaker_min_kn — number — test-facilities: min shaker force, kN
  • thrust_max_mn — number — propulsion: max thrust, mN
  • thrust_min_mn — number — propulsion: min thrust, mN
  • battery_min_wh — number — platforms: min battery capacity, Wh
  • buspower_min_w — number — platforms: min orbit-average power generation, W
  • capacity_min_u — number — deployer: min capacity, U (your satellite size)
  • dipole_min_am2 — number — magnetorquer: min dipole moment, A*m2
  • impulse_min_ns — number — propulsion: min total impulse, N*s
  • paypower_min_w — number — platforms: min orbit-average power available to the payload, W
  • preload_min_kn — number — separation: min preload/holding force, kN
  • reltime_max_ms — number — separation: max release time, ms
  • capacity_max_wh — number — batteries: max capacity, Wh
  • capacity_min_wh — number — battery: min capacity, Wh
  • exclude_company — string — manufacturer names to EXCLUDE, comma-separated (for "not from Sodern")
  • exclude_country — string — countries or a region to EXCLUDE — "China", "Russia, Belarus", "Asia" (for "not Chinese", "non-US")
  • specimen_min_kg — number — test-facilities: mass of your test article the lab must take, kg
  • pointacc_max_deg — number — platforms / pointing mechanisms / ground stations: worst acceptable pointing accuracy, deg (30 arcsec = 0.0083)
  • panel_power_min_w — number — solar panel: min BOL output, W
  • conductance_min_wk — number — thermal strap: min conductance, W/K
  • gyro_range_min_dps — number — IMU: min gyro range, deg/s

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• find_alternatives read-only

  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.

  Parameters:

  • country — string — optional manufacturer country or region
  • product — string — product name (e.g. "RW210", "ST200 star tracker")
  • product_id — integer — product id, instead of the name
  • tolerance_pct — number — allowed deviation from the original, % (default 20, 5–50)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• selection_guide read-only

  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.

  Parameters:

  • category (required) — string — component class (reaction-wheels, star-trackers, platforms, antennas…) or "cubesat"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• find_suppliers read-only

  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.

  Parameters:

  • category (required) — string — component class, e.g. platforms, star-trackers, reaction-wheels (see match_components)
  • bus_v — number — bus voltage the unit must accept, V
  • orbit — string — platforms: LEO | SSO | MEO | GEO | lunar
  • export — string — ITAR-free | EAR99 | ITAR
  • country — string — English country or region (China, Germany, Europe)
  • data_if — string — data interface: CAN, RS-422, SpaceWire…
  • mass_max — number — max unit mass, g
  • prop_type — string — platforms: electric | chemical | any; propulsion: electric | chemical | cold-gas | water
  • accuracy_max — number — star trackers: cross-boresight accuracy, arcsec
  • momentum_min — number — reaction wheels: momentum, N·m·s
  • flight_proven — boolean — only flight-proven products
  • paymass_min_g — number — platforms: payload mass that must fit, g
  • paypower_min_w — number — platforms: orbit-average power for the payload, W
  • exclude_company — string — manufacturer names to EXCLUDE, comma-separated
  • exclude_country — string — countries or a region to EXCLUDE (China, Asia)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• build_budget read-only

  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.

  Parameters:

  • items (required) — array — components of the stack
  • bus_v — number — power bus voltage, V — each item is checked against its supply range

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_component_specs read-only

  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.

  Parameters:

  • ids — array — only these product ids (from match_components)
  • keys — array — only these properties (prop_key values from properties), e.g. ["mass_g","momentum_nms"]
  • limit — integer — products per call (default 10, max 60)
  • offset — integer — continue from paging.next_offset
  • category — string — component class — ONE per call; for several classes call once per class (default reaction-wheels)
  • confidence — string — pass L1 to get only human-verified rows

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_datasheet_digest read-only

  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.

  Parameters:

  • q — string — product name if no id
  • product_id — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search_datasheet_facts read-only

  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).

  Parameters:

  • category (required) — string
  • key (required) — string
  • contains — string — keep only values containing this text

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• ask_datasheet read-only

  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.

  Parameters:

  • q — string — question to one datasheet
  • term — string — exact word/phrase for the category scan, e.g. SpaceWire, ITAR
  • category — string
  • product_id — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• design_stack read-only

  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).

  Parameters:

  • q (required) — string — the task, e.g. "6U CubeSat bus on 12 V with S-band radio and GNSS, star tracker better than 10 arcsec"
  • fixed — array — product ids to keep (locked parts)

  Hints: read-only yes · destructive no · idempotent no · open-world no

• find_data_gaps read-only

  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.

  Parameters:

  • status — string
  • category — string
  • company_id — integer
  • product_id — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• ask_console read-only

  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.

  Parameters:

  • q (required) — string — the question in English or Russian, e.g. "star tracker better than 10 arcsec under 1 kg", "who makes batteries in Germany", "what is TRL"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_fit read-only

  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.

  Parameters:

  • items (required) — array — products of the spacecraft, deployer or ground segment (ids from match_components)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.