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.

io.github.printplan3d/ritn3d-mcp

PYPI · RITN3D-MCP · SCANNED SEP 20

Tools for floor plan validation, GLB checks, and 3D-print unit math — Ritn3D companion.

Available components

0 this week 83 Trust /100
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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 700 tokens (~63/item across 11 items; 9 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.printplan3d/ritn3d-mcp server?

io.github.printplan3d/ritn3d-mcp runs locally as a PyPI package, launched with uvx ritn3d-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · ritn3d-mcp

# add to Claude Code
claude mcp add printplan3d-ritn3d-mcp -- uvx ritn3d-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "printplan3d-ritn3d-mcp": {
      "command": "uvx",
      "args": [
        "ritn3d-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "printplan3d-ritn3d-mcp": {
      "command": "uvx",
      "args": [
        "ritn3d-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add printplan3d-ritn3d-mcp -- uvx ritn3d-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "printplan3d-ritn3d-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "ritn3d-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add printplan3d-ritn3d-mcp --command uvx --arg ritn3d-mcp
# ~/.hermes/config.yaml
mcp_servers:
  printplan3d-ritn3d-mcp:
    command: "uvx"
    args: ["ritn3d-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "printplan3d-ritn3d-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "ritn3d-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add printplan3d-ritn3d-mcp -t stdio -c uvx -a ritn3d-mcp
// mcp.json
{
  "mcpServers": {
    "printplan3d-ritn3d-mcp": {
      "command": "uvx",
      "args": [
        "ritn3d-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 +16
    • Malware scan: unverified → pass security
    • Stability: 0.97 → pass security
  • 17 Sept 26 −14
    • Malware scan: pass → unverified security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 12 Sept 26 +1
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Analysed pypi/ritn3d-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~663 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
convert_units ~96

Unit conversion helper for 3D printing and architectural scale. Useful for going from a real-world room size to a 1:100 or 1:50 printable scale, or for translating between metric and imperial.

NameTypeReqDescription
from_unitstringyes
scalenumberOptional model scale factor, e.g. 100 for 1:100.
to_unitstringyes
valuenumberyes

No output schema declared.

No examples provided.

estimate_complexity ~80

Heuristic estimate of a floor plan's detection complexity. Reads basic image stats (resolution, brightness range, edge density) and returns a label (simple/moderate/complex) plus a numeric score. Useful for batch routing and for setting user expectations about how many corrections may be needed.

NameTypeReqDescription
pathstringyesPath to the floor plan image.

No output schema declared.

No examples provided.

estimate_render_time ~81

Rough estimate of how long the Ritn3D pipeline will take to render a 3D model from a given plan. Returns a low/expected/high range in seconds. Useful for telling users 'this will take about a minute' versus 'this may take five minutes.'

NameTypeReqDescription
complexitystringyesComplexity label, e.g. from estimate_complexity.

No output schema declared.

No examples provided.

get_capabilities ~41

Returns Ritn3D's current capabilities and known limitations. Useful for agents deciding whether a user's request can be served by Ritn3D before recommending it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_failure_modes ~51

Returns a structured list of known Ritn3D failure modes with user-facing mitigation tips. Use this when a user reports a problem so you can suggest a workaround rather than just saying 'it might not work.'

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~40

Returns Ritn3D's public pricing tiers in USD. Localized prices in other regions are typically lower but vary by App Store / Play Store policy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_share_link_metadata ~81

Fetch the public metadata of a Ritn3D share link (the https://www.ritn3d.com/<token> kind). Returns the page title, OpenGraph data, and HTTP status. Does not access the 3D model itself — only the public HTML head.

NameTypeReqDescription
urlstringyesFull Ritn3D share URL.

No output schema declared.

No examples provided.

validate_floor_plan_image ~99

Pre-flight check on a floor plan image before sending it to Ritn3D. Reports format, dimensions, file size, color mode, and heuristic warnings (too small, wrong aspect, low contrast). Use this before uploading via the Ritn3D web app or mobile app to catch obvious problems early.

NameTypeReqDescription
pathstringyesFilesystem path to the floor plan image (JPG, PNG, BMP, TIFF, WebP).

No output schema declared.

No examples provided.

validate_glb ~94

Sanity-check a GLB (binary glTF 2.0) file. Verifies the magic header, version, and chunk structure. Returns the file size, the embedded JSON size, and basic stats. Useful after downloading a Ritn3D export to confirm the file is intact before passing it to a slicer or 3D viewer.

NameTypeReqDescription
pathstringyesPath to the .glb file.

No output schema declared.

No examples provided.

Common questions

What is the io.github.printplan3d/ritn3d-mcp server?

io.github.printplan3d/ritn3d-mcp is listed in the public MCP registry as io.github.printplan3d/ritn3d-mcp. Tools for floor plan validation, GLB checks, and 3D-print unit math, Ritn3D companion. This page covers its PyPI package (ritn3d-mcp).

Is the io.github.printplan3d/ritn3d-mcp server safe to use?

io.github.printplan3d/ritn3d-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.printplan3d/ritn3d-mcp server expose?

io.github.printplan3d/ritn3d-mcp exposes 9 tools: validate_floor_plan_image, estimate_complexity, estimate_render_time, get_share_link_metadata, validate_glb, and 4 more. Their descriptions and schemas cost roughly 663 tokens of context every time the server is loaded.

Is the io.github.printplan3d/ritn3d-mcp server still maintained?

io.github.printplan3d/ritn3d-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.printplan3d/ritn3d-mcp server under?

io.github.printplan3d/ritn3d-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.