com.spacemushroom/materials
REMOTE · SPACEMUSHROOM.COM
Read-only sourced engineering materials data: every value with unit, conditions and source.
Available components
Last scanned (9 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1306 tokens (~118/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://spacemushroom.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spacemushroom.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 79393a913127b1e10eafb70d3fa75188 |
| SANs: spacemushroom.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spacemushroom.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| spacemushroom.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spacemushroom.com/mcp | Verified | 200 | |
| http (plaintext) | http://spacemushroom.com/mcp | HTTPS enforced | 301 | https://spacemushroom.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare Compare materials on one property ~95
Line several materials up on one property, with each value, its conditions and its source. Values are also given in the property's canonical unit (value_canonical), so they can be ranked directly. Values measured under different conditions are listed separately and are not averaged.
| Name | Type | Req | Description |
|---|---|---|---|
| materials | array | yes | Ids from search_materials |
| property | string | yes | For example thermal_runaway_onset or atomic_oxygen_erosion_yield |
No output schema declared.
No examples provided.
find_materials Find materials that meet requirements ~199
Requirements in, candidates out. Each material gets a verdict: pass (every constraint met by a sourced value), fail, or unknown (no data on a constraint, so it cannot be ruled in or out). Every constraint reports pass, fail or no_data and the strongest evidence level behind it (flown, measured, derived, inferred, estimated, predicted). By default only passes and unknowns are returned, passes first. Context narrows which values count: at_temperature (degrees C; values measured at another temperature do not count), flown_only (only values measured in the real space environment), environment, include_failed, limit. Materials with no data on any constraint are not listed: use what_is_missing to see coverage for one material.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | yes | The requirements a material must meet, each a property, an operator and a value |
| context | object | – | Optional narrowing of which values count and how many results to return |
No output schema declared.
No examples provided.
get_material Get a material ~126
The sourced record of one material: sourced numbers with conditions, method and source location, plus uses, hazards, failure modes, corrosion and supply facts. Optionally narrow to one property or fact topic.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id from search_materials, for example "lithium-iron-phosphate" |
| include_facts | boolean | – | Include uses, hazards, failure modes and other facts (default true) |
| property | string | – | Only claims for this property, for example thermal_runaway_onset |
| topic | string | – | Only facts on this topic |
No output schema declared.
No examples provided.
get_term Look up a term ~56
A plain-language definition of a technical term or abbreviation used on material pages, for example ARC, SoC or adiabatic.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The term or abbreviation, for example ARC, SoC or adiabatic |
No output schema declared.
No examples provided.
list_claims List the sourced values of a material ~84
Every current sourced value for one material (optionally one property) in canonical units, with evidence level and a claim_id. Use the claim_id with prove_claim to see the exact source and passage.
| Name | Type | Req | Description |
|---|---|---|---|
| material | string | yes | Material id from search_materials, for example peek |
| property | string | – | Only this property, for example density (see list_properties) |
No output schema declared.
No examples provided.
list_properties List properties ~52
The property names in use, with their canonical unit and whether higher or lower is better. Use these names with get_material and compare.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional text to filter property names, for example density |
No output schema declared.
No examples provided.
prove_claim Prove a value ~64
Everything behind one value: as printed in the source, converted, the evidence level and what it means, the conditions, and each source with the place in it (and the passage where we have it).
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | integer | yes | The claim_id from list_claims |
No output schema declared.
No examples provided.
resolve_designation Resolve a designation ~184
Which material a code names: a UNS number, EN number or name, DIN, JIS, AISI or SAE number, ASTM or AMS specification, or trade name (for example S31600, 1.4401, SUS316, A240). Case, spaces and hyphens do not matter, and a short code also lists the codes that start with it. Each row gives the system, the code, a note (product form or a caveat) and whether the match is exact. A specification such as ASTM A240 covers many grades and returns every material that cites it. A note of "nearest equivalent" means the source itself hedges: do not treat the two as the same grade.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A designation or trade name, for example S31600, 1.4401, SUS316 or A240 |
No output schema declared.
No examples provided.
search_materials Search materials ~107
Find materials by name, abbreviation or formula. Optionally filter by category slug (for example polymers, metals, energy). Returns ids to use with get_material.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug to filter by, for example polymers, metals or energy |
| limit | integer | – | Maximum results to return, 1 to 50 (default 10) |
| query | string | yes | Name, abbreviation or formula, for example "PEEK" or "LiFePO4" |
No output schema declared.
No examples provided.
search_sources Search source passages ~84
Full-text search over short passages quoted from our sources. Returns the passage, the source and the place in it. Passages are still being added, so an empty answer means none indexed yet.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum passages to return, 1 to 20 (default 5) |
| query | string | yes | Words to search for in the quoted source passages |
No output schema declared.
No examples provided.
what_is_missing What data is missing ~80
For one material and a list of properties: which have sourced data (and the strongest evidence) and which have none. "no_data" means not covered yet, not known to be safe.
| Name | Type | Req | Description |
|---|---|---|---|
| material | string | yes | Material id from search_materials |
| properties | array | yes | Property names to check, from list_properties, for example density |
No output schema declared.
No examples provided.
How do I install the com.spacemushroom/materials MCP server?
com.spacemushroom/materials is a hosted endpoint at https://spacemushroom.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · spacemushroom.com
claude mcp add --transport http com-spacemushroom-materials 'https://spacemushroom.com/mcp'
What is the com.spacemushroom/materials MCP server?
com.spacemushroom/materials is an MCP server listed in the public MCP registry as com.spacemushroom/materials. Read-only sourced engineering materials data: every value with unit, conditions and source. This page covers its hosted endpoint (https://spacemushroom.com/mcp).
Is the com.spacemushroom/materials MCP server safe to use?
com.spacemushroom/materials scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.spacemushroom/materials MCP server expose?
com.spacemushroom/materials exposes 11 tools: search_materials, get_material, compare, list_properties, get_term, and 6 more. Their descriptions and schemas cost roughly 1,131 tokens of context every time the server is loaded.
Does the com.spacemushroom/materials MCP server require authentication?
No. We connected to com.spacemushroom/materials without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.spacemushroom/materials MCP server still maintained?
com.spacemushroom/materials is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.spacemushroom/materials MCP server?
VerifyMCP ran 13 checks on com.spacemushroom/materials, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.