Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

claude mcp add --transport http mrd https://newspacemarket.com/mrd-connect/mcp

[mcp_servers.mrd]
url = "https://newspacemarket.com/mrd-connect/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrd": {
      "type": "remote",
      "url": "https://newspacemarket.com/mrd-connect/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "mrd": {
      "type": "http",
      "url": "https://newspacemarket.com/mrd-connect/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=mrd&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbmV3c3BhY2VtYXJrZXQuY29tL21yZC1jb25uZWN0L21jcCJ9"
}

{
  "servers": {
    "mrd": {
      "type": "http",
      "url": "https://newspacemarket.com/mrd-connect/mcp"
    }
  }
}

{
  "mcpServers": {
    "mrd": {
      "httpUrl": "https://newspacemarket.com/mrd-connect/mcp"
    }
  }
}

extensions:
  "mrd":
    enabled: true
    name: "mrd"
    type: streamable_http
    uri: "https://newspacemarket.com/mrd-connect/mcp"
    timeout: 300

Quality 83 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations13 of 14 tools declare readOnlyHint or destructiveHint
warn
tools.directory_hints13 of 14 tools declare all four hints; missing: explain_properties (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
pass
tools.token_costabout 5,969 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability75 · weight 15

warn
stability.changes8 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependencies100 · weight 15

pass
deps.known_vulnsno known advisory in 1 resolved packages
n/a
deps.mcp_sdk_versionthe official MCP SDK is not in the dependency graph
pass
deps.resolvable@newspacemarket/[email protected] resolved: 1 packages

14 tools, about 5,969 tokens to load them all · tool set d74419e3b55d · tools last changed 2026-09-26 · checked 2026-10-19 21:42 UTC

Tool changes

2026-09-26get_component_specschangedinput schema
2026-09-26find_supplierschangedinput schema
2026-09-26find_alternativesadded
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.
2026-09-26match_componentschangeddescription, input schema
before
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. 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.
after · 88% of words in common
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.
2026-09-25get_component_specschangeddescription, input schema
before
The full typed layer of a category — 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.
after · 82% of words in common
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.
2026-09-25find_suppliersadded
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.
2026-09-25selection_guideadded
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.
2026-09-25match_componentschangeddescription, input schema
before
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, ground-stations, sadm, tanks-valves, separation-systems, pointing-mechanisms.
after · 79% of words in common
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. 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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 94 / 100

provenance90

liveness100

freshness85

hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-36d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Dependencies

@newspacemarket/[email protected] npm0 dependencies, resolved · advisories checked 2026-10-19

No known advisory affects this dependency graph.

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://newspacemarket.com/mrd-connect/mcp` streamable-http	none	yes	100%	968 ms	2025-11-25	2026-10-19

package	registry	version	runtime	secrets
`@newspacemarket/mrd-mcp`	npm	1.2.0	–	`MRD_API_KEY`

Tools (14)

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

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.github.newspacemarket-com/mrd",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://newspacemarket.com/mrd-connect/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.2.0",
  "packages": [
    {
      "version": "1.2.0",
      "transport": {
        "type": "stdio"
      },
      "identifier": "@newspacemarket/mrd-mcp",
      "registryType": "npm",
      "registryBaseUrl": "https://registry.npmjs.org",
      "environmentVariables": [
        {
          "name": "MRD_API_KEY",
          "isSecret": true,
          "description": "Optional free API key; raises rate limits five-fold. Request one at https://newspacemarket.com/mrd-connect/"
        }
      ]
    }
  ],
  "repository": {
    "url": "https://github.com/newspacemarket-com/mrd",
    "source": "github"
  },
  "websiteUrl": "https://newspacemarket.com/mrd-connect/",
  "description": "Spacecraft component specs from vendor datasheets: search, digests, facts, gaps, budgets, bus design"
}