mcp-registry/io.github.newspacemarket-com/mrd · v1.2.0
As of 2026-10-20 20:02 UTC, the Newspacemarket Com Mrd MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 7 minutes.
Spacecraft component specs from vendor datasheets: search, digests, facts, gaps, budgets, bus design
Claude Code
claude mcp add --transport http newspacemarket-com-mrd-mcp-server https://newspacemarket.com/mrd-connect/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"newspacemarket-com-mrd-mcp-server": {
"type": "http",
"url": "https://newspacemarket.com/mrd-connect/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: match_components, ~2,692).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~2,092 tokens every session. How to fix →
9 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~2,369 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
1 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
In the last 30 days: 0 tool(s) removed and 15 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.newspacemarket-com%2Fmrd/fixes
{
"name": "explain_properties",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"category"
],
"properties": {
"subtype": {
"type": "string",
"description": "optional subtype slug, e.g. cmg, heatpipe, sequencer"
},
"category": {
"type": "string",
"description": "category slug, e.g. reaction-wheels, deployers, thermal"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.newspacemarket-com/mrd"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.newspacemarket-com/mrd"}) over MCP.
match_components ~2,692 tokensfind_suppliers ~550 tokensget_component_specs ~425 tokenssearch_datasheet_facts ~274 tokensfind_data_gaps ~270 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.newspacemarket-com%2Fmrd?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.newspacemarket-com%2Fmrd?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.newspacemarket-com%2Fmrd.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.newspacemarket-com%2Fmrd.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.newspacemarket-com%2Fmrd?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9dca2aaa90059239…, first seen 2026-10-17, included at leaf 16606 of 34,979. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable search servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 20:02 UTC, the Newspacemarket Com Mrd MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 7 minutes.
Newspacemarket Com Mrd MCP server advertises 14 tools, including ask_console, ask_datasheet, build_budget, check_fit, design_stack.
Point your MCP client at this streamable-http endpoint: https://newspacemarket.com/mrd-connect/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.