Server Details
Spacecraft component specs from vendor datasheets: search, digests, facts, gaps, budgets, bus design
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- newspacemarket-com/mrd
- GitHub Stars
- 1
- Server Listing
- NewSpace Market MRD
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 14 tools
The descriptions are exceptionally detailed and explicitly state when to use each tool, which makes most tools clearly distinct. However, a few pairs are conceptual near-neighbors that could cause misselection: ask_datasheet vs search_datasheet_facts (both scan datasheets across a category) and ask_console vs design_stack (both accept plain-language engineering queries). The strong usage guidance mitigates most confusion.
13 of 14 tools follow a consistent verb_noun snake_case pattern (ask_, find_, get_, match_, search_, explain_, build_, check_, design_). The verbs are semantically grouped (find_alternatives/find_data_gaps/find_suppliers, get_component_specs/get_datasheet_digest), which aids recognition. selection_guide breaks the convention as a noun_noun name, a minor deviation.
14 tools is within the well-scoped 3-15 range, and each tool earns its place for the spacecraft component selection domain. The count reflects the genuine breadth of operations needed: discovery (match/find/search), retrieval (get/ask), analysis (build_budget, check_fit, design_stack), and learning (explain_properties, selection_guide). No tool feels redundant.
The tool surface covers the full selection lifecycle for spacecraft components: learning about properties (explain_properties, selection_guide), discovery (match_components, find_suppliers, find_alternatives, search_datasheet_facts), detailed retrieval (get_component_specs, get_datasheet_digest, ask_datasheet), engineering verification (build_budget, check_fit, design_stack), and gap analysis (find_data_gaps). As a read-only catalog server, there are no dead ends or obvious missing operations.
Available Tools
14 toolsask_consoleARead-onlyIdempotentInspect
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.
Inputs: q (required).
ask_datasheetARead-onlyIdempotentInspect
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.
Inputs: q, term, category, product_id.
build_budgetARead-onlyIdempotentInspect
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.
Inputs: items (required), bus_v.
check_fitARead-onlyIdempotentInspect
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.
Inputs: items (required).
design_stackARead-onlyInspect
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).
Inputs: q (required), fixed.
explain_propertiesAInspect
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.
Inputs: category (required), subtype.
find_alternativesARead-onlyIdempotentInspect
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.
Inputs: country, product, product_id, tolerance_pct.
find_data_gapsARead-onlyIdempotentInspect
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.
Inputs: status, category, company_id, product_id.
find_suppliersARead-onlyIdempotentInspect
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.
Inputs: category (required), bus_v, orbit, export, +11 more.
get_component_specsARead-onlyIdempotentInspect
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.
Inputs: ids, keys, limit, offset, +2 more.
get_datasheet_digestARead-onlyIdempotentInspect
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.
Inputs: q, product_id.
match_componentsARead-onlyIdempotentInspect
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.
Inputs: band, test, bus_v, group, +86 more.
search_datasheet_factsARead-onlyIdempotentInspect
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).
Inputs: key (required), category (required), contains.
selection_guideARead-onlyIdempotentInspect
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.
Inputs: category (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Turn datasheets into source-backed JSON contracts, pinout matrices, and KiCad CAD for AI agents.
Search real parts with datasheet-provenance specs, check compatibility and compose priced BOMs.
Read-only catalog of drone and eVTOL components: products, makers, specs and sources.
Orbital data center & space AI compute tracker MCP: projects, launches, orbits, alerts. 100 free/day
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides AI agents with instant, structured access to electronic component datasheets, pinouts, and electrical specifications without requiring PDF uploads. It enables seamless part searching, design validation, and side-by-side component comparisons across major hardware providers.1476 npm12MIT
- AlicenseAqualityBmaintenanceSearch 419,000+ LLM-extracted space regulatory filings from the FCC, ITU, UNOOSA, and FAA. Semantic search, entity dossiers, spectrum-band holdings, launch licenses, filing trends, and alerts.221MIT
- AlicenseNot gradedqualityDmaintenanceAuto-managed SPICE kernels for heliophysics missions. Enables querying spacecraft positions, trajectories, and coordinate transforms via natural language.57 PyPIMIT
- AlicenseAqualityDmaintenanceProvides LLMs with direct access to official vendor PDF documentation for electronics components (TI, ST, ADI) via a local SQLite full-text index and PDF retrieval tools.62ISC
Glama MCP Gateway
Add one secure layer between your agents and this server.