Almond MCP Server

almond-mcp PyPI v0.5.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Almond - MCP server for Rhino 8 with a semantic scene layer: curated furniture/drawing/diagram libraries, audited Karamba capsules, structured retrieval (SQLite FTS5 + R-tree scene ledger), and a TCP bridge into Rhino (RhinoAlmondBridge, port 5000)

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (rhino_bridge.py)MTC-SRC-002

In the server's implementation (`rhino_bridge.py:234`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: exec(script_code, exec_globals) guids = [str(g) for g in exec_globals.get("created_

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server rhino_bridge.py

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • apply_drawing_styleno sensitive capability
  • assign_materialno sensitive capability
  • create_design_sceneno sensitive capability
  • create_generation_planno sensitive capability
  • execute_rhino_scriptno sensitive capability
  • export_asset_contractno sensitive capability
  • export_structural_reportno sensitive capability
  • get_blender_helper_scriptno sensitive capability
  • get_design_sceneno sensitive capability
  • get_diagram_assetno sensitive capability
Show 31 more tools ↓
  • get_drawing_assetno sensitive capability
  • get_drawing_recipeno sensitive capability
  • get_generation_planno sensitive capability
  • get_ikea_furnitureno sensitive capability
  • get_logic_by_idno sensitive capability
  • get_retrieval_statusno sensitive capability
  • import_asset_contractno sensitive capability
  • import_drawing_hatch_patternsno sensitive capability
  • list_capsulesno sensitive capability
  • list_diagram_assetsno sensitive capability
  • list_drawing_assetsno sensitive capability
  • list_drawing_recipesno sensitive capability
  • list_ikea_furnitureno sensitive capability
  • list_libraryno sensitive capability
  • list_materialsno sensitive capability
  • place_diagram_assetno sensitive capability
  • place_drawing_assetno sensitive capability
  • place_ikea_furnitureno sensitive capability
  • publish_objects_to_chestnutno sensitive capability
  • publish_to_chestnutno sensitive capability
  • register_scene_instanceno sensitive capability
  • remove_design_roomno sensitive capability
  • remove_scene_instanceno sensitive capability
  • run_gh_definitionno sensitive capability
  • search_diagram_assetsno sensitive capability
  • search_drawing_assetsno sensitive capability
  • search_ikea_furnitureno sensitive capability
  • update_generation_stepno sensitive capability
  • upsert_design_roomno sensitive capability
  • validate_scene_layoutno sensitive capability
  • validate_structureno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.0 latest A 92/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/almond-mcp/badge.svg)](https://mcptrustchecker.com/registry/almond-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/almond-mcp"><img src="https://mcptrustchecker.com/registry/almond-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/almond-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan almond-mcp --online --registry pypi

Use the free API → How scoring works

More in Web, Search & Scraping