# com.spacemushroom/materials (remote · spacemushroom.com)

Read-only sourced engineering materials data: every value with unit, conditions and source.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `spacemushroom.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom.md), [page](https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom)

## Channel facts

- Endpoint: `https://spacemushroom.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http com-spacemushroom-materials 'https://spacemushroom.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-spacemushroom-materials": {
      "url": "https://spacemushroom.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-spacemushroom-materials": {
      "type": "http",
      "url": "https://spacemushroom.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-spacemushroom-materials]
url = "https://spacemushroom.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-spacemushroom-materials": {
      "type": "remote",
      "url": "https://spacemushroom.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-spacemushroom-materials --url 'https://spacemushroom.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-spacemushroom-materials:
    url: "https://spacemushroom.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-spacemushroom-materials": {
      "Transport": "http",
      "Url": "https://spacemushroom.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-spacemushroom-materials -t streamable-http -u 'https://spacemushroom.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-spacemushroom-materials": {
      "type": "http",
      "url": "https://spacemushroom.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +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.

### 2026-11-03 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 71)

First indexed and scored.

## MCP tools (11)

### `search_materials` (~107 tokens)

Search materials

Find materials by name, abbreviation or formula. Optionally filter by category slug (for example polymers, metals, energy). Returns ids to use with get_material.

Input parameters:

- `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, required): Name, abbreviation or formula, for example "PEEK" or "LiFePO4"

### `get_material` (~126 tokens)

Get a material

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.

Input parameters:

- `id` (string, required): 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

### `compare` (~95 tokens)

Compare materials on one property

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.

Input parameters:

- `materials` (array, required): Ids from search_materials
- `property` (string, required): For example thermal_runaway_onset or atomic_oxygen_erosion_yield

### `list_properties` (~52 tokens)

List properties

The property names in use, with their canonical unit and whether higher or lower is better. Use these names with get_material and compare.

Input parameters:

- `query` (string): Optional text to filter property names, for example density

### `get_term` (~56 tokens)

Look up a term

A plain-language definition of a technical term or abbreviation used on material pages, for example ARC, SoC or adiabatic.

Input parameters:

- `term` (string, required): The term or abbreviation, for example ARC, SoC or adiabatic

### `find_materials` (~199 tokens)

Find materials that meet requirements

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.

Input parameters:

- `constraints` (array, required): 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

### `list_claims` (~84 tokens)

List the sourced values of a material

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.

Input parameters:

- `material` (string, required): Material id from search_materials, for example peek
- `property` (string): Only this property, for example density (see list_properties)

### `prove_claim` (~64 tokens)

Prove a value

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

Input parameters:

- `claim_id` (integer, required): The claim_id from list_claims

### `what_is_missing` (~80 tokens)

What data is missing

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.

Input parameters:

- `material` (string, required): Material id from search_materials
- `properties` (array, required): Property names to check, from list_properties, for example density

### `resolve_designation` (~184 tokens)

Resolve a designation

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.

Input parameters:

- `code` (string, required): A designation or trade name, for example S31600, 1.4401, SUS316 or A240

### `search_sources` (~84 tokens)

Search source passages

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.

Input parameters:

- `limit` (integer): Maximum passages to return, 1 to 20 (default 5)
- `query` (string, required): Words to search for in the quoted source passages

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71

## Common questions

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

## Links

- Remote endpoint: https://spacemushroom.com/mcp
- Repository: https://github.com/simulsarker007/space-mushroom-mcp
- Website: https://spacemushroom.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom.json
- HTML version of this page: https://verifymcp.io/servers/com-spacemushroom-materials/spacemushroom