RackArchitect MCP
MCP server · mcp.rackarchitect.dev · found in a public list · checked since 2026-10-30
Live, handshake completed · latest check
https://mcp.rackarchitect.dev/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
connect_cablesdefine_custom_blueprintdisconnect_cablesexport_deliverablesget_device_blueprintinit_rackmodify_equipmentmount_equipmentplan_external_endpointssearch_catalogundo_redovalidate_rack
- Tools
- 12
- This list since
- 2026-10-30
- First listed to us
- 2026-10-30
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptsresourcestools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
search_catalog query form_factor mount_type category max_depth_mm min_poe_budget_watts accepted_slot_type → status summary data issuesget_device_blueprint slug* → status summary data issuesdefine_custom_blueprint blueprint* → status summary data issuesinit_rack project_name standard* u_height* rail_depth_mm* enclosure_type front_door_clearance_mm rear_clearance_mm → status summary data issuesmount_equipment instance_id* blueprint_slug* hostname u_position face parent_carrier_id slot_id → status summary data issuesmodify_equipment instance_id* action* u_position new_u_position face new_face parent_carrier_id slot_id hostname new_hostname remove_connected_cables → status summary data issuesconnect_cables cables* → status summary data issuesdisconnect_cables cable_ids instance_id → status summary data issuesplan_external_endpoints patch_panel_instance_id* start_port_number entry_position groups endpoints auto_connect_switch_instance_id auto_connect_switch_start_port clear_existing → status summary data issuesvalidate_rack → status summary data issuesexport_deliverables formats output_dir → status summary data issuesundo_redo action* → status summary data issues
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-30. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, handshake completed HTTP 200 | 1135 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_39496504acf07476