MCP server for Japanese labor and social insurance law — e-Gov API, MHLW rulings, JAISH safety and health rulings
Nothing to run from here
Ottosim — Simulation 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.
94/100
trust score
13
downloads a day
local
runs on your machine
1k
downloads in 30d
What it does
Thermal, structural, modal, DC, and laminar-flow studies from STEP via Gmsh and Elmer.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ottosim-simulation-mcp '--' npx -y simulation-mcp-server
# 2 — ask your agent for something these tools do
# get_capabilities, inspect_model, query_model and 7 more
Ottosim — Simulation costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OTAll 3 servers
ottonic3 servers
3 categories
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. This one runs on your machine: your client starts Ottosim — Simulation as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user ottosim-simulation-mcp '--' npx -y simulation-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: 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 your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Discover implemented and benchmarked physics workflows actually available in this installation. Unavailable physics are never accepted for preparation.
No parameter schema on file.
Snapshot a local STEP file and inspect SI-normalized geometry. Supply exactly one URI or revisioned STEP artifact. Returned entity tags are scoped to the model inspection; labels are hints, never engineering assignments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uri | string | no | — |
| source | no | — |
List inspected model entities, optionally filtered by dimension. Entity IDs and labels belong to this exact inspection revision. Use returned IDs to define study selections.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | yes | The inspection artifact returned by inspect_model. | |
| dimension | no | Keep only entities of this dimension: 2 = surfaces, 3 = solids. | |
| cursor | string | no | Pagination cursor from the previous page. |
| limit | integer | no | Entities per page, at most 200 (default 100). |
Validate a complete study draft and explain missing or unsupported inputs without launching Gmsh or Elmer. The study shape, per-physics fields and a worked example are in get_capabilities.study.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| study | object | yes | — |
Queue validation, meshing and solver-input generation for an available study type in the background. Transient thermal requires density, heat capacity, a uniform initial temperature, timestep and step count. Transient flow uses first-order BDF with explicit quiescent initial velocity. Returns a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| study | yes | — |
Execute an immutable prepared study asynchronously. Returns a jobId; use inspect_job, list_jobs, query_results or cancel_job.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prepared | yes | — |
Inspect preparation or solver job status, diagnostics and available artifacts. Pass waitMs to wait for a terminal state instead of polling; interrupted jobs are not resumed automatically.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | yes | Job id from prepare_study or run_study. | |
| waitMs | integer | no | — |
Recover recent solver jobs after losing conversation context. Returns up to 100 jobs, newest first.
No parameter schema on file.
Retrieve bounded evidence for a solver job, including its job ID, source model and prepared-study reference, status, convergence, observations and acceptance, distinct output fields, and a paginated artifact page. Summaries are returned when explicitly requested with include:['summaries'], or as a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | yes | Solver job id returned by run_study. | |
| include | array | no | — |
| observations | array | no | Keep only these observation ids (as defined in the study). |
| time | number | no | — |
| limit | integer | no | Artifacts per page, at most 500 (default 100). |
| cursor | string | no | Pagination cursor from the previous page. |
Cancel an active preparation or solver job owned by this server. Child processes are stopped before cancellation is reported; partial artifacts are retained.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | yes | Job id of the active preparation or solver job to stop. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Ottosim — Simulation 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: —
ATrust score 94 / 100
Release 0.3.0 · scanned 31 Oct 2026
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 score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest4a3d0deaf0427675a841b9d312e8b7a2a3d2e041e05c19d869ee3490f3de2689
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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 digest4a3d0deaf0427675
Scanned2026-10-31
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.0. Pin a release below and the command asks for exactly that one.
0.3.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 Ottosim — Simulation 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.