MCP server for Japanese labor and social insurance law — e-Gov API, MHLW rulings, JAISH safety and health rulings
Nothing to run from here
Materials is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read-only sourced engineering materials data: every value with unit, conditions and source.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http materials-mcp https://spacemushroom.com/mcp
# 2 — ask your agent for something these tools do
# search_materials, get_material, compare and 8 more
Materials costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SPAll 1 server
spacemushroom1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http materials-mcp https://spacemushroom.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find materials by name, abbreviation or formula. Optionally filter by category slug (for example polymers, metals, energy). Returns ids to use with get_material.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Name, abbreviation or formula, for example "PEEK" or "LiFePO4" |
| category | string | no | Category slug to filter by, for example polymers, metals or energy |
| limit | integer | no | Maximum results to return, 1 to 50 (default 10) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The id from search_materials, for example "lithium-iron-phosphate" |
| property | string | no | Only claims for this property, for example thermal_runaway_onset |
| topic | string | no | Only facts on this topic |
| include_facts | boolean | no | Include uses, hazards, failure modes and other facts (default true) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property | string | yes | For example thermal_runaway_onset or atomic_oxygen_erosion_yield |
| materials | array | yes | Ids from search_materials |
The property names in use, with their canonical unit and whether higher or lower is better. Use these names with get_material and compare.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional text to filter property names, for example density |
A plain-language definition of a technical term or abbreviation used on material pages, for example ARC, SoC or adiabatic.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | The term or abbreviation, for example ARC, SoC or adiabatic |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| constraints | array | yes | The requirements a material must meet, each a property, an operator and a value |
| context | object | no | Optional narrowing of which values count and how many results to return |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| material | string | yes | Material id from search_materials, for example peek |
| property | string | no | Only this property, for example density (see list_properties) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim_id | integer | yes | The claim_id from list_claims |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| material | string | yes | Material id from search_materials |
| properties | array | yes | Property names to check, from list_properties, for example density |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | A designation or trade name, for example S31600, 1.4401, SUS316 or A240 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to search for in the quoted source passages |
| limit | integer | no | Maximum passages to return, 1 to 20 (default 5) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Materials or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 2 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest51f7aa5e2461c7513dd27e7bed6cd6518b2fd5a3428e804a2dc76a7f5f5024d2
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_materials | no tags | |
| get_material | no tags | |
| compare | no tags | |
| list_properties | no tags | |
| get_term | no tags | |
| find_materials | no tags | |
| list_claims | no tags | |
| prove_claim | no tags | |
| what_is_missing | no tags | |
| resolve_designation | no tags | |
| search_sources | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest51f7aa5e2461c751
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Materials can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.