Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ottoref — Standards MCP Server

NPM · STANDARDS-MCP-SERVER

ISO 286 limits and fits, ISO 2768 tolerances, material properties, and process limits.

81 Trust /100

Last scanned (20 hours ago)

Scores higher than 68% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 4 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ottonic/standards-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1664 tokens (~138/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Nov 26 +10
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.90 ▲ functional
  • 31 Oct 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/standards-mcp-server@0.3.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ottonic/standards-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ottonic/standards-mcp-server/.github/workflows/release-please.yml@refs/heads/main
Rekor log index 3606748354
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:196e7a921bbfe4b5a1e8e9c337d9c6735e7c6df6097a96cc84fabca1d00d07d7341bbdeafddf4496600c866381a48621c8abba50312beed7b0c81649c

Background: How many MCP packages publish verified provenance →

Dependencies 16 packages
Packages resolved 16
Stale 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~1,497 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fit ~157

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 interfere. This reports the geometry of the fit, not whether it is the right choice for a joint, which depends on function and is the caller's decision.

NameTypeReqDescription
holestringyesHole tolerance class, e.g. H7.
nominalnumberyesNominal size in millimetres, shared by the hole and shaft.
shaftstringyesShaft tolerance class, e.g. g6 or n6.

Structured output declared, but exposes no named fields.

No examples provided.

general_tolerance ~173

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 shorter side of the angle rather than the nominal size. A general tolerance applies only where the drawing gives no individual tolerance, so check for one first.

NameTypeReqDescription
kindstring–Which table to read: linear dimensions (default), broken edges such as chamfers and external radii, or angular dimensions. They have different values.
nominalnumberyesNominal size, or the shorter side of an angle.
tolerance_classstringyesClass letter from the drawing note, e.g. m.

Structured output declared, but exposes no named fields.

No examples provided.

general_tolerance_complies ~158

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 not establish process capability.

NameTypeReqDescription
kindstring–Which table applies. Default: linear.
nominalnumberyesNominal size, or the shorter side of an angle.
stated_deviationnumberyesThe deviation the drawing actually states for this dimension, in millimetres (or degrees for angular). Sign is ignored: the tables are symmetric.
tolerance_classstringyesClass letter from the drawing note, e.g. m.

Structured output declared, but exposes no named fields.

No examples provided.

iso286_applicability ~81

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.

NameTypeReqDescription
designationstringyesTolerance class in standard notation, e.g. H7, j5 or N9.

Structured output declared, but exposes no named fields.

No examples provided.

it_grade ~103

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.

NameTypeReqDescription
gradestringyesStandard tolerance grade in ISO notation: IT01, IT0, or IT1 to IT18.
nominalnumberyesNominal size in millimetres.

Structured output declared, but exposes no named fields.

No examples provided.

limits_of_size ~119

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 resulting limits suit a joint is an engineering decision.

NameTypeReqDescription
designationstringyesTolerance class, e.g. H7 or g6.
nominalnumberyesNominal size in millimetres.

Structured output declared, but exposes no named fields.

No examples provided.

list_standards ~89

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 reason rather than approximated. Use iso286_applicability for exact size intervals of an ISO 286 class.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

material_coverage ~74

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 and no high-temperature data.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

material_properties ~186

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 handbook values, not design allowables: every value is tagged basis: typical. Use them to compare materials, estimate mass, or supply an indicative modulus to an analysis; obtain an allowable from a qualified source before relying on a strength margin. An unmatched designation means this reference does not hold it, not that the material does not exist.

NameTypeReqDescription
materialstringyesMaterial designation, e.g. "6061-T6" or "304".
propertystring–Restrict the answer to one property, so the response stays small.

Structured output declared, but exposes no named fields.

No examples provided.

process_feasibility ~212

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 thickness when the limit needs it. A result inside the limits is not a promise that a shop can make the part, or an estimate of what it costs. Pair this with a measured wall or hole size from a CAD server to answer whether a part suits a process.

NameTypeReqDescription
featurestringyesWhich limit to check.
measurednumberyesThe measured value for the feature, in millimetres (or degrees for draft).
processstringyesWhich process the feature is being made by.
thicknessnumber–Material thickness in millimetres. Required when the limit is expressed as a ratio of thickness, which is common for sheet metal — the error says so if it is missing.

Structured output declared, but exposes no named fields.

No examples provided.

process_limits ~99

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 rules of thumb for geometric feasibility, not a specific shop's capability, and they say nothing about cost or lead time.

NameTypeReqDescription
processstringyesWhich process to describe.

Structured output declared, but exposes no named fields.

No examples provided.

process_list ~46

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.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Ottoref — Standards MCP Server server?

Ottoref — Standards MCP Server runs locally as an npm package, launched with npx -y standards-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · standards-mcp-server

# add to Claude Code
claude mcp add ottonic-standards-mcp-server -- npx -y standards-mcp-server
Common questions

What is the Ottoref — Standards MCP Server server?

Ottoref — Standards MCP Server is listed in the public MCP registry as io.github.ottonic/standards-mcp-server. ISO 286 limits and fits, ISO 2768 tolerances, material properties, and process limits. This page covers its npm package (standards-mcp-server).

Is the Ottoref — Standards MCP Server server safe to use?

Ottoref — Standards MCP Server scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Ottoref — Standards MCP Server server expose?

Ottoref — Standards MCP Server exposes 12 tools: list_standards, limits_of_size, iso286_applicability, fit, it_grade, and 7 more. Their descriptions and schemas cost roughly 1,497 tokens of context every time the server is loaded.

Is the Ottoref — Standards MCP Server server still maintained?

Ottoref — Standards MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Ottoref — Standards MCP Server server under?

Ottoref — Standards MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.