RackArchitect MCP server
io.github.itAlex240/rack-architect-mcpitAlex240streamable-httpv0.7.8Scanned
Hosted Remote MCP & 3D/2D Rack-as-Code planner, 5-stage validator, CAD SVG/BOM & STL generator.
12 tools: 5 can delete or cancel things, 4 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RackArchitect MCP server can do
The RackArchitect MCP server is published by the GitHub account itAlex240. It has 12 tools. It can delete or cancel things (5 tools: init_rack, modify_equipment, disconnect_cables, plan_external_endpoints and 1 more) and create or change data (4 tools: define_custom_blueprint, mount_equipment, connect_cables and undo_redo). 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 0.7.8.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 5Claude Code: deny
disconnect_cablesRemove specific cables by identifier or strip all cables attached to a mounted device or modular carrier from the active rack, then re-evaluate PoE budgets and plug clearances.No findings
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove specific cables by identifier or strip all cables attached to a mounted device or modular carrier from the active rack, then re-evaluate PoE budgets and plug clearances. Supply a non-empty 'cable_ids' list, 'instance_id', or both to disconnect their union; 'instance_id' matches both 'from' and 'to' endpoints across a carrier and its child sub-modules while leaving external patch-panel drops intact, whereas omitting both or passing only an empty list returns status 'INVALID' with a PORT_NOT_FOUND issue and zero mutations. Valid calls push an undo snapshot, persist rack.yaml atomically, and return removed IDs, remaining cable count, and updated validation results, succeeding idempotently when targeted IDs are already absent. Use when rewiring ports while keeping hardware mounted; use connect_cables to add or replace cables, or modify_equipment with action 'remove' to delete a device and its cables.
Annotations the server declares
- title: Disconnect Cables by ID or Device Instance
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
export_deliverablesGenerate 2D elevation and wiring SVGs, a Markdown BOM, a binary 3D GLB scene, and parametric OpenSCAD or watertight STL 3D-print models for the active rack project.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Generate 2D elevation and wiring SVGs, a Markdown BOM, a binary 3D GLB scene, and parametric OpenSCAD or watertight STL 3D-print models for the active rack project. Omitting 'formats' exports all six types; 'carrier-scad' and 'carrier-stl' emit one file per mounted modular carrier, switch cradle, or printable cover panel and emit zero files when none are mounted, while 'output_dir' resolves relative paths within the project directory and creates missing folders. Local stdio execution writes deterministic filenames—elevation.svg, wiring-schematic.svg, BOM.md, rack-scene.glb, and <slug>.scad or <slug>.stl—overwriting same-named files in place, whereas hosted remote sessions stream in-memory HTTPS download URLs; neither mode mutates rack state or undo history. Use after validate_rack confirms a valid layout; use validate_rack instead for read-only validation and ASCII elevation inspection without generating export files.
Annotations the server declares
- title: Export 2D SVG, BOM, 3D GLB, and 3D-Print Deliverables
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
init_rackInitialize a new rack project and destructively reset the active rack.yaml state to an empty enclosure with the specified width standard, U height, and rail depth.No findings
Why it is in this group
- The name "init_rack" says "init": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Initialize a new rack project and destructively reset the active rack.yaml state to an empty enclosure with the specified width standard, U height, and rail depth. Overwrites the current enclosure and clears all mounted devices, child sub-modules, cables, and external endpoints, while pushing the previous project state onto the in-memory undo stack for recovery via undo_redo. 'project_name' sets the title used in exported schematics and BOMs, 'rail_depth_mm' plus 'rear_clearance_mm' bounds total +Z chassis and rear plug depth before wall collision, and 'front_door_clearance_mm' is enforced only when 'enclosure_type' has a closed front door. Use when starting a rack design from scratch or changing enclosure dimensions; use validate_rack to inspect the current rack, or modify_equipment to move or remove individual devices.
Annotations the server declares
- title: Initialize and Reset Rack Enclosure
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
modify_equipmentMove, rename, or destructively remove an existing mounted device or child sub-module in the active rack, recalculate 3D cable splines, and re-run 5-stage validation.No findings
Why it is in this group
- The name "modify_equipment" says "modify": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Move, rename, or destructively remove an existing mounted device or child sub-module in the active rack, recalculate 3D cable splines, and re-run 5-stage validation. 'instance_id' resolves across top-level devices and carrier sub-modules, and required fields depend on 'action': 'move' updates 'u_position' and 'face' on rackmount gear or 'slot_id' and optional 'parent_carrier_id' across carriers for sub-modules with primary fields taking precedence over 'new_*' aliases, 'rename' updates or clears 'hostname', and 'remove' cascades to child sub-modules plus attached cables and external endpoints when 'remove_connected_cables' is true. Pushes the prior state onto the undo stack and updates rack.yaml atomically, or returns status 'INVALID' without mutating state when 'instance_id' or a target carrier is unknown. Use to update or delete a mounted instance; use mount_equipment to add new hardware, or disconnect_cables to remove cables while keeping devices mounted.
Annotations the server declares
- title: Move, Rename, or Remove Mounted Equipment
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
plan_external_endpointsTerminate external building or room cable drops onto the rear RJ45 ports of a mounted patch panel without consuming rack U slots, and optionally auto-create labeled Cat6A front pat…No findings
Why it is in this group
- The description's first verb is "terminate": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Terminate external building or room cable drops onto the rear RJ45 ports of a mounted patch panel without consuming rack U slots, and optionally auto-create labeled Cat6A front patch cables to a mounted switch. 'groups[]' batch-generates drops first—with 'custom_labels[]' overriding numbered 'label_prefix' entries per index—followed by 'endpoints[]', allocating sequential free rear ports from 'start_port_number' and sequential free switch RJ45 ports from 'auto_connect_switch_start_port'. Setting 'clear_existing' destructively removes prior external drops on 'patch_panel_instance_id' and their front patch cables before allocation, while unmounted patch-panel or switch IDs return status 'INVALID' without mutating state. Use for off-rack building wiring entering the enclosure; never mount room endpoints via mount_equipment, and use connect_cables for purely internal rack-to-rack links.
Annotations the server declares
- title: Terminate External Building Cable Drops on Patch Panel
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
connect_cablesConnect or update a batch of up to 128 power and network cables between mounted device ports in the active rack, computing 3D Catmull-Rom splines, commercial length bins, and PoE o…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Connect or update a batch of up to 128 power and network cables between mounted device ports in the active rack, computing 3D Catmull-Rom splines, commercial length bins, and PoE or power budgets. Each entry in 'cables[]' upserts in place by 'cable_id' while leaving all other cables and mounted equipment untouched, pushes a recoverable undo snapshot, and persists rack.yaml atomically; port, speed, PoE, or clearance violations return status 'INVALID' with remediation_suggestions instead of throwing. Within each cable, endpoint 'face' is required only on pass-through couplers such as patch panels exposing identical 'port_id' values on both faces, 'preferred_portal_u' applies only to front-to-rear transitions, and 'vlan_id' or 'ip_cidr' annotate logical network links. Use when both endpoint devices are mounted inside the rack; use disconnect_cables to remove cables, or plan_external_endpoints to terminate incoming building cable drops on a patch panel.
Annotations the server declares
- title: Connect and Route Inter-Device Cables
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
define_custom_blueprintValidate and register a custom hardware blueprint into the active catalog so unlisted equipment can be mounted.1 finding
Why it is in this group
- The description's first verb is "validate": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "define_custom_blueprint" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "validate": a word for reading.
Description, as the server wrote it Validate and register a custom hardware blueprint into the active catalog so unlisted equipment can be mounted. Pass the entire specification inside the top-level 'blueprint' object: 'blueprint.slug' must use lowercase kebab-case, ports may combine explicit 'ports[]' with repeating 'port_groups[]' macros whose coordinates fit strictly within 'blueprint.geometry' without overlapping, and 'slots[]' applies only when 'mount_type' is 'modular-carrier' whereas 'slot_compatibility' applies to 'sub-module'. Persists YAML to the local custom-catalog folder in stdio mode or session memory on remote servers, overwrites same-slug custom entries without touching mounted rack state or undo history, and returns status 'INVALID' instead of throwing on validation errors. Use only after search_catalog confirms hardware is unlisted; use mount_equipment instead to place an already registered blueprint into the rack.
Annotations the server declares
- title: Register Custom Hardware Blueprint
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mount_equipmentMount a new hardware device instance onto a rack unit or into a modular carrier bay in the active rack.yaml project and run 5-stage validation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Mount a new hardware device instance onto a rack unit or into a modular carrier bay in the active rack.yaml project and run 5-stage validation. 'instance_id' must be unique across both top-level devices and nested sub-modules, 'blueprint_slug' must reference an existing catalog or custom slug, and placement uses two mutually exclusive modes: 'u_position' with optional 'face' where the device's full U span fits within 1..u_height, or 'parent_carrier_id' plus a compatible 'slot_id' for sub-modules. Precondition errors such as duplicate 'instance_id', unknown 'blueprint_slug', or missing carriers return status 'INVALID' without mutating state, whereas 3D collision or PoE issues persist the mount, push an undo snapshot, and return remediation_suggestions. Use to add a new device instance; use modify_equipment to move, rename, or remove an existing instance, or plan_external_endpoints for off-rack room cable drops.
Annotations the server declares
- title: Mount Equipment into Rack Unit or Carrier Slot
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
undo_redoTraverse the per-project in-memory history ring buffer of up to 50 snapshots to revert the latest rack mutation or reapply a reverted mutation, updating rack.yaml atomically.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Traverse the per-project in-memory history ring buffer of up to 50 snapshots to revert the latest rack mutation or reapply a reverted mutation, updating rack.yaml atomically. Setting 'action' to 'undo' steps backward across rack-state mutations—excluding catalog-only define_custom_blueprint calls and read-only tools—and pushes the displaced state onto the redo stack, whereas 'redo' is available only immediately after 'undo' because any new rack mutation flushes the redo stack. Calling either action when its target stack is empty is a safe no-op returning applied=false without throwing. Use to roll back an unintended batch change or accidental init_rack reset; use modify_equipment or disconnect_cables instead to edit specific items without reverting intermediate steps.
Annotations the server declares
- title: Undo or Redo Rack State Mutation
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_device_blueprintRetrieve the complete hardware specification, millimeter port coordinates, electrical and PoE ratings, and carrier slot geometry for a single catalog blueprint.No findings
Why it is in this group
- The name "get_device_blueprint" says "get": a word for reading.
Description, as the server wrote it Retrieve the complete hardware specification, millimeter port coordinates, electrical and PoE ratings, and carrier slot geometry for a single catalog blueprint. The 'slug' parameter requires a case-sensitive exact match in lowercase kebab-case vendor-model-variant format against the built-in or session custom catalog; partial substrings or uppercase characters do not match. Returns the full blueprint in one unpaginated payload with repeating port_groups pre-expanded into up to 256 flat ports[] entries, or returns status 'INVALID' with a BLUEPRINT_NOT_FOUND issue and candidate slugs instead of throwing. Use when you already know the target slug and need exact port_id or slot_id values for mount_equipment or connect_cables; use search_catalog instead to discover unknown slugs by criteria.
Annotations the server declares
- title: Retrieve Hardware Device Blueprint Details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_catalogSearch and filter the local hardware catalog to discover compatible rackmount devices, modular carriers, and sub-modules before mounting.No findings
Why it is in this group
- The name "search_catalog" says "search": a word for reading.
Description, as the server wrote it Search and filter the local hardware catalog to discover compatible rackmount devices, modular carriers, and sub-modules before mounting. All supplied filters combine with logical AND: 'form_factor' and its alias 'mount_type' accept width shorthands '10inch', '19inch', and '6inch' that match both direct rackmount gear and modular carriers, 'accepted_slot_type' matches both carrier bays and compatible sub-modules, and 'max_depth_mm' bounds chassis depth excluding plug clearance. Returns all matches from the bounded catalog in one unpaginated response sorted in deterministic registration order, with built-in blueprints followed by custom blueprints. Call with no arguments to list the full catalog; use get_device_blueprint to inspect expanded port coordinates for a known slug, or define_custom_blueprint to register unlisted hardware.
Annotations the server declares
- title: Search Hardware Blueprint Catalog
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_rackInspect the active rack.yaml state and run all 5 deterministic validation stages covering mechanical bounds, 3D depth and plug clearances, PoE and power budgets, cable compatibilit…No findings
Why it is in this group
- The name "validate_rack" says "validate": a word for reading.
Description, as the server wrote it Inspect the active rack.yaml state and run all 5 deterministic validation stages covering mechanical bounds, 3D depth and plug clearances, PoE and power budgets, cable compatibility, and thermal limits. Takes no parameters, performs zero state or undo-stack mutations, and returns the ASCII front and rear elevation diagram, power utilization summary, and all diagnostic issues with remediation_suggestions. Sets status to 'INVALID' instead of throwing whenever any validation ERROR is present. Use to inspect currently mounted equipment or verify zero errors before exporting; use export_deliverables instead to generate SVG, BOM, GLB, or 3D-print files.
Annotations the server declares
- title: Inspect and Validate Active Rack State
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:24 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (5 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.rackarchitect.dev/mcp: tools/list returned 12 tools to an anonymous client, including init_rack (destructive), modify_equipment (destructive), disconnect_cables (destructive), plan_external_endpoints (destructive), export_deliverables (destructive) and 4 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "define_custom_blueprint" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "validate": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools8 changed.~8 changedView diff
- Changed:define_custom_blueprintChanges thingsinputSchema
- Changed:disconnect_cablesDeletes or cancelsinputSchema
- Changed:export_deliverablesDeletes or cancelsdescriptioninputSchemaannotations
- Changed:get_device_blueprintOnly readsinputSchema
- Changed:modify_equipmentDeletes or cancelsinputSchema
- Changed:mount_equipmentChanges thingsinputSchema
- Changed:plan_external_endpointsDeletes or cancelsinputSchema
- Changed:search_catalogOnly readsinputSchema
Tools12 changed.~12 changedView diff
- Changed:connect_cablesChanges thingsdescription
- Changed:define_custom_blueprintChanges thingsdescription
- Changed:disconnect_cablesDeletes or cancelsdescription
- Changed:export_deliverablesChanges thingsdescription
- Changed:get_device_blueprintOnly readsdescription
- Changed:init_rackDeletes or cancelsdescription
- Changed:modify_equipmentDeletes or cancelsdescription
- Changed:mount_equipmentChanges thingsdescription
- Changed:plan_external_endpointsDeletes or cancelsdescription
- Changed:search_catalogOnly readsdescription
- Changed:undo_redoChanges thingsdescription
- Changed:validate_rackOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:export_deliverablesChanges thingsdescription
Install
Pinned to version 0.7.8. Values in angle brackets are yours to fill in.
claude mcp add --transport http rack-architect https://mcp.rackarchitect.dev/mcpclaude mcp add --transport http rack-architect https://mcp.rackarchitect.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__rack-architect__search_catalog",
"mcp__rack-architect__get_device_blueprint",
"mcp__rack-architect__validate_rack"
],
"ask": [
"mcp__rack-architect__define_custom_blueprint",
"mcp__rack-architect__mount_equipment",
"mcp__rack-architect__connect_cables",
"mcp__rack-architect__undo_redo"
],
"deny": [
"mcp__rack-architect__init_rack",
"mcp__rack-architect__modify_equipment",
"mcp__rack-architect__disconnect_cables",
"mcp__rack-architect__plan_external_endpoints",
"mcp__rack-architect__export_deliverables"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rack-architect. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.itAlex240/rack-architect-mcp/verify?hash=a9ea5428de5a7c4b83f7bf22d1e18edee6da189baf8804e3a11867bea06cef6a" | jq -e '.changed == false'Pinned hash a9ea5428de5a, from Nov 17, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.itAlex240/rack-architect-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.itAlex240/rack-architect-mcp)Source: MCP Registry · repository. Synced Nov 3, 2026, 21:17 UTC.
RackArchitect MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RackArchitect MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RackArchitect MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: init_rack, modify_equipment, disconnect_cables, plan_external_endpoints and export_deliverables.
Can the RackArchitect MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RackArchitect MCP server have?
- 12 tools: 5 destructive, 4 write, 3 read. init_rack, modify_equipment, disconnect_cables, plan_external_endpoints, export_deliverables, define_custom_blueprint, mount_equipment, connect_cables and 4 more.
Does the RackArchitect MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RackArchitect MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RackArchitect MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.