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

io.github.ChanMeng666/archlang-mcp

NPM · @CHANMENG666/ARCHLANG-MCP · SCANNED AUG 3

Compile, describe, lint, validate, score and repair multi-storey and curved ArchLang floor plans.

+47 this week 82 Trust /100
Trust breakdown (6 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 →

Supply Chain Security88
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (172 of 173), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (172 of 173), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ChanMeng666/archlang). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
  • 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 1409 tokens (~100/item across 14 items; 9 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @chanmeng666/archlang-mcp

# add to Claude Code
claude mcp add chanmeng666-archlang-mcp -- npx -y @chanmeng666/archlang-mcp
# add to Codex CLI
codex mcp add chanmeng666-archlang-mcp -- npx -y @chanmeng666/archlang-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chanmeng666-archlang-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@chanmeng666/archlang-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add chanmeng666-archlang-mcp --command npx --arg -y --arg @chanmeng666/archlang-mcp
# ~/.hermes/config.yaml
mcp_servers:
  chanmeng666-archlang-mcp:
    command: "npx"
    args: ["-y", "@chanmeng666/archlang-mcp"]
// mcp.json
{
  "mcpServers": {
    "chanmeng666-archlang-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chanmeng666/archlang-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.

  • 2 Aug 26 +77
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Malware scan: unverified → pass security
    • The attested source repository moved: ChanMeng666/archlang security
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Tool coverage: unverified → 100 functional
    • Schema quality: unverified → 100 functional
    • Licence: MIT functional
  • 1 Aug 26 −21
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
  • 31 Jul 26 −9
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 35

    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 3 Aug 2026 · Analysed npm/@chanmeng666/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
ChanMeng666/archlang
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/ChanMeng666/archlang/.github/workflows/release.yml@refs/tags/v1.24.0
Rekor log index:
2255993095
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:b2bca58416e438d709cd78c565ed4328978ffcd5b3cafd9129a13ee6cb2fb27384a8f8a3211d24b551cc12f30bbcc827d9b739b77f3ff0bb7039cd1e2
Discovery method:
attestation_endpoint
Dependencies 172 packages

172 packages in the resolved dependency tree · 170 deprecated · 60 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 9 exposed · ~1,288 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.

Tool Tokens
compile ~286

Compile ArchLang `.arch` source (or a Plan-JSON object) to an SVG floor plan, or to a zero-dependency ASCII text plan (format:"txt"). Returns the rendered output plus diagnostics — each a byte span, line/col, catalogued E_/W_ code, and a machine-applicable fix. Errors are DATA, never exceptions: read `diagnostics` and correct the source. A MULTI-STOREY plan (`level <n> { … }`) is a set of drawings: `output` is the lowest storey and every storey comes back in `pages[]` ({ level, name, output }), so pass `level` to render just one.

NameTypeReqDescription
accessiblebooleanEmit <title>/<desc>/role/aria accessibility metadata (SVG only).
formatstringsvg (default) or txt (zero-dependency ASCII).
levelintegerRender only this storey of a multi-storey plan. An undeclared level is an error, not a guess.
overlaystringDraw an opt-in circulation overlay (SVG only).
plan_jsonobjectPlan JSON (RPLAN shape) as an alternative to `source`; converted to .arch then compiled.
sourcestringArchLang source (a `plan "…" { … }`). Provide this OR plan_json.

No output schema declared.

No examples provided.

complete ~65

Completion items in scope at a source BYTE offset (the LSP `completion()` core): keywords, element names, ids, enum values — for structured or assisted authoring.

NameTypeReqDescription
atintegeryesSource byte offset to complete at.
sourcestringyesArchLang source.

No output schema declared.

No examples provided.

describe ~165

Semantic facts about a plan without rendering: rooms (areas, bboxes, adjacency, uses, and the exact shape — `floor_polygon` for a `room polygon`, `floor_circle` for a `room circle`, whose area is exact πR²), doors (what they connect), windows, circulation (walk distance / bottleneck width / detour), zones, storeys (`levels[i]` carries the same facts per floor) with the shafts that join them and which storeys stay reachable (`vertical`), the drawing extent (`bbox`, `bbox_outer`), `freedom` (which positions are hand-authored vs resolver-derived), and totals. The channel a text-only agent uses to VERIFY that a plan matches intent.

NameTypeReqDescription
sourcestringyesArchLang source.

No output schema declared.

No examples provided.

fix ~134

Apply the machine-applicable fixes a compile attaches to its diagnostics — the SYNTACTIC corrector (off-wall openings → the attachment form, out-of-range positions clamped, …), distinct from `repair`'s geometric solver. Bounded fixpoint (≤4 passes; a pass that raises the error count is rolled back). `unsafe:true` also applies `maybe-incorrect` fixes. Returns { ok, passes, applied, skipped, source }.

NameTypeReqDescription
sourcestringyesArchLang source to fix.
unsafebooleanAlso apply `maybe-incorrect` fixes (default: machine-applicable only).

No output schema declared.

No examples provided.

lint ~97

Advisory `W_*` soundness warnings as data: unreachable room, windowless bedroom, too-narrow door, blocked doorway, furniture through a wall, circuitous path, and more. `profile` selects a ruleset (e.g. "residential-basic", "accessibility-advisory").

NameTypeReqDescription
profilestringAdvisory ruleset name (default: the built-in ruleset).
sourcestringyesArchLang source.

No output schema declared.

No examples provided.

repair ~89

The explicit source-to-source corrector (ADR 0006): push furniture out of walls / doorways / swing arcs, separate overlaps, relocate wrong-room fixtures, snap floating pieces to walls. Returns corrected `.arch` source + a change log. It NEVER adds doors or windows — that is a design choice; use `suggest` for topology.

NameTypeReqDescription
sourcestringyesArchLang source to correct.

No output schema declared.

No examples provided.

score ~147

The continuous intent-satisfaction METER: check a brief's intent JSON (per /intent.schema.json) against a plan and report how much it satisfies. Returns { ok, satisfied, total, score, subscores, violations } where `score` is satisfied/total in [0,1] (an empty intent scores 1). It MEASURES, it never gates — so you can watch a plan approach the brief across edits. A malformed intent returns `{ ok:false, intentErrors }` (data, never a throw).

NameTypeReqDescription
briefobjectyesA brief's intent JSON (per /intent.schema.json) to measure against.
sourcestringyesArchLang source.

No output schema declared.

No examples provided.

suggest ~92

Advisory topology suggestions as DATA — never applied (ADR 0005). For a room with no path back, a building with no entrance, a bath reachable only through a bedroom, or a windowless bedroom, returns ready-to-paste `door`/`window` statements (attachment form, furniture-aware) plus a rationale, for the agent to choose among and insert.

NameTypeReqDescription
sourcestringyesArchLang source.

No output schema declared.

No examples provided.

validate ~213

The ship gate: parse + resolve + lint in one pass, no render. `strict:true` makes advisory warnings fail too. Optional `graph` checks the plan's interior-door adjacency against an intended room graph (`{ room: [neighbours] }`); a mismatch fails. Optional `intent` (a brief's expectations per /intent.schema.json) is checked against the plan — a failing GATING assertion (room count / existence / area / total-area / windows) fails validate, while adjacency and reachability are advisory and only score. A malformed intent returns `{ ok:false, intentErrors }` (data, never a throw). Returns { ok, diagnostics, graph?, intent? }.

NameTypeReqDescription
graphobjectIntended interior-door adjacency: { room: [neighbour rooms] }.
intentobjectA brief's intent JSON (per /intent.schema.json); gating assertions fail validate.
sourcestringyesArchLang source.
strictbooleanAdvisory warnings fail too.

No output schema declared.

No examples provided.