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.

OpenCalque

NPM · OPENCALQUE

Draw 2D floor plans as JSON: walls, doors, rooms, furniture. Check, measure, export PDF, DXF, SVG.

Available components

68 Trust /100

Last scanned (9 hours ago)

Scores higher than 39% of npm servers

Category Design and Media

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to laurent512/opencalque). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1053 tokens (~105/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Malware scan: unverified → pass ▲ security
    • Package version: 1.14.0 → 2.0.0 functional
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Package version: 1.12.0 → 1.14.0 functional
    • Package version: 1.12.0 → 1.13.0 functional
  • 18 Nov 26 +27
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 1.00 ▲ functional
  • 17 Nov 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Package version: 1.10.1 → 1.12.0 functional
    • Package version: 1.10.1 → 1.11.0 functional
    • Package version: 1.10.1 → 1.10.2 functional
  • 16 Nov 26 81

    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 21 Nov 2026 · Analysed npm/opencalque@2.0.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 laurent512/opencalque
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/laurent512/opencalque/.github/workflows/release.yml@refs/tags/v2.0.0
Rekor log index 4033059015
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:edc44a685390c78bad9f7db1de025d19a81752020e4e8d0faea436f44184640490260f661cc76038dd460990fbfc833f0d151cbbd218827923fe3ee9a

Background: How many MCP packages publish verified provenance →

Dependencies 13 packages
Packages resolved 13
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~973 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
apply_operations ~135

Changes the drawing. Takes a list of operations and applies them in order as a single edit. The list is all-or-nothing: if any operation is invalid nothing changes and the error is returned so you can correct it. Returns the ids of the nodes that were added, lists any property you wrote that the format does not know (usually a misspelling), which was kept but has no effect, and under "problems" what the edit left wrong: a room that does not close and the wall end that may be why, walls drawn over each other, a door outside its wall.

NameTypeReqDescription
operationsarrayyes–

No output schema declared.

No examples provided.

check_drawing ~92

Lists what is wrong with a page, whoever did it: rooms that have no floor, with the wall ends that may be why, rooms that share one, walls drawn over each other, doors and windows outside a wall, past its end or over one another. Each problem says what to do about it.

NameTypeReqDescription
pagestring–Id of a page or component. Leave it out for the whole drawing.

No output schema declared.

No examples provided.

describe_drawing ~57

Returns a short summary of the drawing: its name, layers, pages and components with what each holds, and what is being worked on and selected. Start here when you do not know the drawing: it is much smaller than read_document.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

measure_drawing ~135

Returns what a page holds, measured from what is drawn: each room with its floor area and perimeter, each wall with its length, doors and windows by size, floors and walls by material, and objects placed. Areas are in m², lengths in m, volumes in m³, thicknesses and the sizes of doors and windows in mm. A room whose walls do not close has an area of 0.

NameTypeReqDescription
ofarray–Which parts to return. Leave it out for all of them.
pagestring–Id of a page or component. Leave it out for the one being worked on.

No output schema declared.

No examples provided.

open_drawing ~75

Chooses the drawing the other tools work on: a .opencalque file. It is created, empty, when it does not exist and "create" is true. Use an absolute path.

NameTypeReqDescription
createboolean–Create it when it does not exist.
filestringyesPath of the drawing.

No output schema declared.

No examples provided.

read_controls ~112

Says what controls what on a page, from its control links: each switch, dimmer or push button with the lights and sockets it controls, and through which of its ports; the objects that need control and have none (lights no switch turns on), under "uncontrolled"; and those that control nothing, under "idle". It describes the plan, it does not check an installation against any rule.

NameTypeReqDescription
pagestring–Id of a page or component. Leave it out for the one being worked on.

No output schema declared.

No examples provided.

read_document ~117

Returns the current drawing as JSON: its layers, shared colours, materials, dimension styles and nodes. Pass "ids" to get only those nodes, with everything inside the groups among them, or "container" (a page, component or group id) to get what it holds. Use it when the drawing was too large to include with the request, or to check the result of an edit.

NameTypeReqDescription
containerstring–Id of a page, component or group.
idsarray–Ids of the nodes to read.

No output schema declared.

No examples provided.

read_guide ~88

Explains how drawings are stored and edited: the types of node, the parametric objects there are, the operations, and what is not obvious from the schema. Read it once before your first edit. With "type", returns the JSON Schema of that type of node instead.

NameTypeReqDescription
typestring–A type of node, such as wall or room, to get its JSON Schema.

No output schema declared.

No examples provided.

view_drawing ~109

Shows you the drawing as it is printed: a picture of a page or component, or of part of it, and which coordinates it covers. Use it to check what you drew, and "area" to look closer at a corner or a room.

NameTypeReqDescription
areaobject–The part to show, in drawing millimetres. Leave it out for everything on the page.
pagestring–Id of a page or component. Leave it out for the one being worked on.

No output schema declared.

No examples provided.

view_image ~53

Shows you a picture placed in the drawing, such as an imported floor plan, together with where it sits so you can convert positions in the picture to drawing coordinates.

NameTypeReqDescription
nodestringyesId of the image node.

No output schema declared.

No examples provided.

Install

How do I install the OpenCalque MCP server?

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

npm · opencalque

# add to Claude Code
claude mcp add laurent512-opencalque -- npx -y opencalque mcp
Common questions

What is the OpenCalque MCP server?

OpenCalque is an MCP server listed in the public MCP registry as io.github.laurent512/opencalque. Draw 2D floor plans as JSON: walls, doors, rooms, furniture. Check, measure, export PDF, DXF, SVG. This page covers its npm package (opencalque).

Is the OpenCalque MCP server safe to use?

OpenCalque scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 OpenCalque MCP server expose?

OpenCalque exposes 10 tools: read_guide, open_drawing, apply_operations, read_document, describe_drawing, and 5 more. Their descriptions and schemas cost roughly 973 tokens of context every time the server is loaded.

Is the OpenCalque MCP server still maintained?

OpenCalque is still listed as active in the MCP registry. We last reached this channel on 21 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 OpenCalque MCP server under?

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

What did VerifyMCP test on the OpenCalque MCP server?

VerifyMCP ran 15 checks on OpenCalque, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about OpenCalque: Malware scan. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.