# com.spacemushroom/materials

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

- name: com.spacemushroom/materials
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 96/100
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.spacemushroom%2Fmaterials
- tools: https://api.protogrid.dev/v1/servers/com.spacemushroom%2Fmaterials/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-12d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 94 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 2 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 24 of 24 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 7,055 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 83 (weight 15)

- warn `stability.changes`: 24 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 24, about 7,055 tokens to load them all
- tool set hash: 63a078b02d714a936b72ca188eb8235f
- tools last changed: 2026-11-05T15:27:37.920Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.spacemushroom/materials.svg)](https://protogrid.dev/servers/com.spacemushroom/materials)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-05 `compare_products` added
  - Put 2 to 6 products side by side: kind, maker, size / mass / orbit, depth label, counts, the materials each uses (and which are shared or unique), the materials per part function, the spec rows they have in common, standards, organizations and what each does not publish. Use it to choose between comparable products or to see how a design differs ("CubeSat Kit structure vs EnduroSat structures"). It reads the same sourced records as get_product; open that for the quotes. Specs are aligned by label, so differences in wording show as separate rows.
- 2026-11-05 `product_graph` added
  - The network around a product as nodes and edges: connected products (engine part of vehicle, launched on, heritage, built on, successor), the organizations (makers, suppliers, operators), the materials, and for the product and its direct neighbours also the parts with their material and supplier. Use it to follow a chain: vehicle -> stage -> engine -> part -> material -> supplier, for example product_graph of the Space Launch System at depth 2. Every edge carries its relation, role, status, quote and source. Nodes of type unresolved are names a source gave that are not products here yet. depth is the number of product-to-product hops (0 to 3, default 1). For depth 2 or more consider include_parts false to keep the answer small. No edge means not recorded, not absent.
- 2026-11-05 `vehicles_for_engine` added
  - Which vehicles and stages use an engine, from stated relations, with the stage or role, the quote and the source: "where is the Merlin 1D used", "which vehicles fly the RL10". vehicle_known false means a source names a vehicle for this engine that is not a product here (only the name is kept). Accepts an id, title or alias (RL10, Merlin, BE-4).
- 2026-11-05 `engines_for_vehicle` added
  - Which engines a launcher, stage or spacecraft uses, from relations a source states (engine part of vehicle, vehicle carries engine). Each engine comes with its stage or role (role, note), the quote and source, its makers and suppliers, and the material ids in it, so you can go on to get_product for the engine or products_using_material for its alloys. engine_known false means a source names the engine for this vehicle but the engine is not a product here yet (only its name is kept). Accepts an id, title or alias (F9, SLS).
- 2026-11-05 `products_by_maker` added
  - Every product an organization is linked to, with its role on each (maker, contractor, supplier, operator, agency), the relation status, the quote and the source: "which products does Aerojet Rocketdyne have", "what did Almatech build". The organization is matched by id or part of its name. role narrows to a role containing that text, for example supplier-like words ("tanks") or "prime contractor". Only stated links are listed.
- 2026-11-05 `orgs_for` added
  - The organizations behind one product, each with its relation (produced_by_org, supplied_by, operated_by), its role, the relation status and the quote and source: makers, agencies, prime contractors, suppliers of named parts, operators. With include_components (default true) it also lists the organizations behind the products that are part of this one, so "who makes the engines used on Vulcan Centaur" is answered with via_product naming the engine. Suppliers appear only where a source states them: no row means not stated, not that there is no supplier.
- 2026-11-05 `standards_for` added
  - The specifications named by products: standards listed for a product (with what they are used for) and the standard written on each part (anodising, chromate, welding, composites ...), each with the part function, the quote and the source where there is one. Give a product ("which standards does the Pumpkin CubeSat Kit structure cite"), a part function ("which standards are used on structural parts"), or both. The function tag is derived from the wording; the standard names are as the sources print them. An empty answer means none named in the sources read.
- 2026-11-05 `materials_used_by_function` added
  - Which materials products use for a kind of part, with how many products and parts, example products, and the forms, finishes and standards that come with each: "I am designing a 3U CubeSat structure for LEO: what materials, forms, finishes and standards do comparable products use" = part_function structure + kind structure + size 3U. Narrow the set of products with the same filters as find_products (category, kind, size, orbit, maker, text, bom_depth). Rows are ranked by number of products. The function tags are derived from part names; counts are of what the catalogue holds, not a survey of the industry. Use the material ids with get_material, and the example product ids with get_product.
- 2026-11-05 `products_using_material` added
  - Every product that uses a material, with the parts, the form, finish, standard and part number, the quote and the source for each: "which products use aluminium 6061 and for which part", "what flew with Kapton and with what finish or standard". The material is an id (find it with search_materials, or from get_product.materials). part_function narrows to parts with one function. Works for materials with a page (material_state profile) and for reserved ids (state reserved: the id is known from products but has no page yet). Products also listed the material in their flat materials list appear under listed. Orbit and size tags tell you what kind of mission it flew on. An empty answer means no catalogued product names that material.
- 2026-11-05 `product_parts` added
  - The flat parts list of one product in source order: assembly, part, function, material (and material id), form, finish, standard, part number, supplier, part specs, quote and source. Use it when you need the parts and not the whole record, for example "the thermal control parts of Parker Solar Probe" (part_function thermal control) or "which parts of Falcon 9 are aluminium" (material). Accepts an id, title or alias. An empty list means no such parts were published in the sources read.

Full history: https://api.protogrid.dev/v1/servers/com.spacemushroom%2Fmaterials/changes

## Remotes

- https://spacemushroom.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (24)

- `compare`: 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.
- `compare_products`: Put 2 to 6 products side by side: kind, maker, size / mass / orbit, depth label, counts, the materials each uses (and which are shared or unique), the materials per part function, the spec rows they have in common, standards, organizations and what each does not publish. Use it to choose between comparable products or to see how a design differs ("CubeSat Kit structure vs EnduroSat structures"). It reads the same sourced records as get_product; open that for the quotes. Specs are aligned by label, so differences in wording show as separate rows.
- `engines_for_vehicle`: Which engines a launcher, stage or spacecraft uses, from relations a source states (engine part of vehicle, vehicle carries engine). Each engine comes with its stage or role (role, note), the quote and source, its makers and suppliers, and the material ids in it, so you can go on to get_product for the engine or products_using_material for its alloys. engine_known false means a source names the engine for this vehicle but the engine is not a product here yet (only its name is kept). Accepts an id, title or alias (F9, SLS).
- `find_materials`: 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.
- `find_products`: Search the catalogue of space products (satellites, platforms, structures, launchers, engines, spacesuits, rovers, observatories, stations) by what they are, who makes them, what they are made of and how. Call it first when you design or study a device: "comparable 3U CubeSat structures" = kind structure + size 3U; "who flies aluminium 6061" = material aluminium-6061; "which products use anodised parts per MIL-A-8625" = finish + standard; "launchers by SpaceX" = category launchers + maker. All filters are optional and combine (AND). text matches every word against names, aliases (F9, Orlan, EMU), summaries, specs, features, parts, materials and organizations. Returns, per product, its id (use it with get_product), maker, kind, category, size / mass / orbit tags, a depth label (full, partial or materials-only: how complete its parts list is), counts of parts, materials, specs and unverified quotes, and the page. It does not return the parts: call get_product or product_parts for those. An empty result means no product in this catalogue matches, not that none exists.
- `get_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.
- `get_product`: The whole record of one product: specs, features, the parts tree (assemblies, parts, material, form, finish, standard, part number, supplier, function), the materials it uses (ids that work with get_material), standards, the organizations behind it (maker, contractors, suppliers, operators), relations to other products (engine part of vehicle, launched on, heritage), photos with credits, and what_is_missing. Call it to study a device: "what is Perseverance's heat shield made of and what heritage does it have", "what is Starship made of and what is not published". Accepts an id, a title or an alias (F9, Orlan, EMU, Webb). Every row has its source URL, its quote and quote_status. what_is_missing is computed: the depth label (full, partial, materials-only), what the sources do not publish, parts without a material, parts without a source, materials with no page yet, relations to names that are not products here, and the count of unverified quotes. The answer can be long for big vehicles: use sections to ask only for what you need, and part_function to cut the parts.
- `get_term`: A plain-language definition of a technical term or abbreviation used on material pages, for example ARC, SoC or adiabatic.
- `list_claims`: 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.
- `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.
- `materials_used_by_function`: Which materials products use for a kind of part, with how many products and parts, example products, and the forms, finishes and standards that come with each: "I am designing a 3U CubeSat structure for LEO: what materials, forms, finishes and standards do comparable products use" = part_function structure + kind structure + size 3U. Narrow the set of products with the same filters as find_products (category, kind, size, orbit, maker, text, bom_depth). Rows are ranked by number of products. The function tags are derived from part names; counts are of what the catalogue holds, not a survey of the industry. Use the material ids with get_material, and the example product ids with get_product.
- `orgs_for`: The organizations behind one product, each with its relation (produced_by_org, supplied_by, operated_by), its role, the relation status and the quote and source: makers, agencies, prime contractors, suppliers of named parts, operators. With include_components (default true) it also lists the organizations behind the products that are part of this one, so "who makes the engines used on Vulcan Centaur" is answered with via_product naming the engine. Suppliers appear only where a source states them: no row means not stated, not that there is no supplier.
- `product_graph`: The network around a product as nodes and edges: connected products (engine part of vehicle, launched on, heritage, built on, successor), the organizations (makers, suppliers, operators), the materials, and for the product and its direct neighbours also the parts with their material and supplier. Use it to follow a chain: vehicle -> stage -> engine -> part -> material -> supplier, for example product_graph of the Space Launch System at depth 2. Every edge carries its relation, role, status, quote and source. Nodes of type unresolved are names a source gave that are not products here yet. depth is the number of product-to-product hops (0 to 3, default 1). For depth 2 or more consider include_parts false to keep the answer small. No edge means not recorded, not absent.
- `product_parts`: The flat parts list of one product in source order: assembly, part, function, material (and material id), form, finish, standard, part number, supplier, part specs, quote and source. Use it when you need the parts and not the whole record, for example "the thermal control parts of Parker Solar Probe" (part_function thermal control) or "which parts of Falcon 9 are aluminium" (material). Accepts an id, title or alias. An empty list means no such parts were published in the sources read.
- `products_by_maker`: Every product an organization is linked to, with its role on each (maker, contractor, supplier, operator, agency), the relation status, the quote and the source: "which products does Aerojet Rocketdyne have", "what did Almatech build". The organization is matched by id or part of its name. role narrows to a role containing that text, for example supplier-like words ("tanks") or "prime contractor". Only stated links are listed.
- `products_using_material`: Every product that uses a material, with the parts, the form, finish, standard and part number, the quote and the source for each: "which products use aluminium 6061 and for which part", "what flew with Kapton and with what finish or standard". The material is an id (find it with search_materials, or from get_product.materials). part_function narrows to parts with one function. Works for materials with a page (material_state profile) and for reserved ids (state reserved: the id is known from products but has no page yet). Products also listed the material in their flat materials list appear under listed. Orbit and size tags tell you what kind of mission it flew on. An empty answer means no catalogued product names that material.
- `prove_claim`: 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).
- `resolve_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.
- `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.
- `search_products`: Ranked full-text search over everything written about the products: names and aliases, summaries, specs, features, parts, materials, finishes, standards and organizations. Use it when you have a description rather than exact filters ("ablative heat shield on a Mars rover", "regeneratively cooled engine", "thermal blankets for CHEOPS"); use find_products when you can name a kind, size, maker or material. Returns the best matches first with a short snippet of the matching text and the page; open one with get_product. An empty answer means no catalogued text matches those words.
- `search_sources`: 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.
- `standards_for`: The specifications named by products: standards listed for a product (with what they are used for) and the standard written on each part (anodising, chromate, welding, composites ...), each with the part function, the quote and the source where there is one. Give a product ("which standards does the Pumpkin CubeSat Kit structure cite"), a part function ("which standards are used on structural parts"), or both. The function tag is derived from the wording; the standard names are as the sources print them. An empty answer means none named in the sources read.
- `vehicles_for_engine`: Which vehicles and stages use an engine, from stated relations, with the stage or role, the quote and the source: "where is the Merlin 1D used", "which vehicles fly the RL10". vehicle_known false means a source names a vehicle for this engine that is not a product here (only the name is kept). Accepts an id, title or alias (RL10, Merlin, BE-4).
- `what_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.