Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Ottoref — Standards 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.
100/100
trust score
10
downloads a day
local
runs on your machine
1k
downloads in 30d
What it does
ISO 286 limits and fits, ISO 2768 tolerances, material properties, and process limits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ottoref-standards-mcp '--' npx -y standards-mcp-server
# 2 — ask your agent for something these tools do
# list_standards, limits_of_size, iso286_applicability and 9 more
Ottoref — Standards 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 Ottoref — Standards 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 ottoref-standards-mcp '--' npx -y standards-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
12 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.
List the standards this server implements, and what within each one is not covered. Call this first when a question mentions a standard, so you know whether the value you need is available before you promise an answer. Coverage is partial by design: unimplemented values are refused with a stated…
No parameter schema on file.
Return the upper and lower deviations, and the resulting limits, for one tolerance class at one nominal size, such as 36H7 or 36g6. Uppercase is a hole, lowercase a shaft. Values are millimetres and are deviations from the nominal size. Use this to interpret a toleranced dimension; whether the…
No parameter schema on file.
List the exact nominal-size intervals where one ISO 286 tolerance class is supported, such as H7, j5 or N9. Use this before relying on a class across a size range; omitted intervals are not inferred.
No parameter schema on file.
Return the resulting fit between one hole class and one shaft class at the same nominal size, such as 12 H7/h6: the type (clearance, transition or interference), the minimum and maximum clearance, and the maximum interference. Values are millimetres. A negative minimum clearance means the fit can…
No parameter schema on file.
Return the standard tolerance value for one IT grade at one nominal size, in micrometres and millimetres, with the size step it came from. Use this when a drawing or a calculation needs the tolerance width itself, rather than the limits of a specific class.
No parameter schema on file.
Return the deviation that a general-tolerance note such as ISO 2768-m implies for one dimension, so an unmarked dimension can be checked. The tables differ by what they cover: linear dimensions, broken edges (external radii and chamfer heights), and angular dimensions, which are keyed by the…
No parameter schema on file.
Compare a stated deviation numerically against the ISO 2768-1 general-tolerance value for one dimension. This is only a numeric comparison: first establish that the dimension has no individual tolerance indication, because the general tolerance applies only to unmarked dimensions. The result does…
No parameter schema on file.
Look up indicative material properties for a common metal or plastic by designation, such as 6061-T6, 304 or Ti-6Al-4V. Returns density, yield and ultimate strength, Young's modulus, Poisson's ratio, elongation, thermal expansion and maximum service temperature, all in SI. These are TYPICAL…
No parameter schema on file.
List what the material reference holds and what it does not. Call this when a material was not found, or before promising a property, so a gap is visible rather than assumed. The reference is limited to typical values for common metals and plastics: it holds no design allowables, no fatigue data…
No parameter schema on file.
Describe what a manufacturing process can hold: minimum wall thickness, minimum hole-to-edge and hole-to-bend distances, minimum internal corner radius, bend radius, draft angle, pocket depth-to-width ratio. Call process_feasibility to test one measured feature against these. These are published…
No parameter schema on file.
Compare one measured feature against a manufacturing process's limits and report whether it is within, marginal, or beyond them. Some limits are expressed as a ratio of material thickness rather than an absolute size — a 1 mm hole is fine in thin sheet and difficult in thick plate — so supply the…
No parameter schema on file.
List the manufacturing processes this server has limits for, and which features each one covers. Call this first when a question names a process, so an unsupported process is visible before a check fails.
No parameter schema on file.
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 Ottoref — Standards 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 100 / 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 score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest097f833fb896035c28051029f799a20aa8dab1ace545e9105b7d70ce3a06c0cf
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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. minimal 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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digest097f833fb896035c
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 Ottoref — Standards 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.