Home / MCP registry index / ai.structupath/steel-tools
ai.structupath/steel-tools
ai.structupath/steel-tools in the official MCP registry.
Endpoint https://www.structupath.ai/api/mcp.
The registry describes it as: Steel takeoff, weight and gauge calculators plus RFQ, RFI, NCR and Bluebeam markup generators.
We read its 14 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
steel_gauge_thickness steel_plate_weight steel_shape_weight steel_connection_reference steel_bolt_pretension steel_pipe_schedule steel_section_weight steel_mtr_check steel_takeoff_weight steel_coating_area steel_rfq_generate steel_pdf_markup steel_rfi_generate steel_ncr_generate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-structupath-steel-tools)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.