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.

ai.structupath/steel-tools

REMOTE · WWW.STRUCTUPATH.AI · SCANNED OCT 4

Steel takeoff, weight and gauge calculators plus RFQ, RFI, NCR and Bluebeam markup generators.

0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2470 tokens (~176/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ai.structupath/steel-tools MCP server?

ai.structupath/steel-tools is a hosted endpoint at https://www.structupath.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.structupath.ai

# add to Claude Code
claude mcp add --transport http ai-structupath-steel-tools 'https://www.structupath.ai/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-structupath-steel-tools": {
      "url": "https://www.structupath.ai/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-structupath-steel-tools": {
      "type": "http",
      "url": "https://www.structupath.ai/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-structupath-steel-tools]
url = "https://www.structupath.ai/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-structupath-steel-tools": {
      "type": "remote",
      "url": "https://www.structupath.ai/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-structupath-steel-tools --url 'https://www.structupath.ai/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-structupath-steel-tools:
    url: "https://www.structupath.ai/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-structupath-steel-tools": {
      "Transport": "http",
      "Url": "https://www.structupath.ai/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-structupath-steel-tools -t streamable-http -u 'https://www.structupath.ai/api/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-structupath-steel-tools": {
      "type": "http",
      "url": "https://www.structupath.ai/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Aug 26 0
    • Tool coverage: 95% → 83% ▼ functional
    • Schema quality: 145 → 176 ▼ functional
    • Server version: 1.5.0 → 1.7.0 functional
    • New tool “steel_coating_area” functional
    • New tool “steel_ncr_generate” functional
    • New tool “steel_rfi_generate” functional
    • New tool “steel_takeoff_weight” functional
  • 13 Aug 26 0
    • Tool coverage: 100% → 95% ▼ functional
    • Schema quality: 123 → 145 ▼ functional
    • Schema quality: excellent → good functional
    • Server version: 1.3.0 → 1.5.0 functional
    • New tool “steel_pdf_markup” functional
    • New tool “steel_rfq_generate” functional
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 4 Oct 2026 · Probed https://www.structupath.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.structupath.ai CN=YR1,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 RSA 2048 SHA256-RSA 6a14e5ca520bcb6fa5f3c1565de74b2f855
SANs: www.structupath.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.structupath.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
structupath.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.structupath.ai/api/mcp Verified 200
http (plaintext) http://www.structupath.ai/api/mcp HTTPS enforced 308 https://www.structupath.ai/api/mcp
MCP tools · 14 exposed · ~2,470 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
steel_bolt_pretension ~100

RCSC minimum pretension for A325/A490 structural bolts by diameter, with the turn-of-the-nut rotation when a bolt length is given. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
diastringyesBolt diameter in inches — fraction ("3/4") or decimal (0.75)
length_innumber–Optional bolt length in inches, for the turn-of-the-nut rotation

No output schema declared.

No examples provided.

steel_coating_area ~197

Surface area to coat for an AISC shape: ft² per foot from the cross-section perimeter, piece/lot area with length and qty, optional interior faces for galvanized tubes and gallons at a supplied coverage rate. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
coverage_sqft_per_galnumber–Optional practical coverage rate from the coating datasheet, to estimate gallons
designationstringyesAISC designation, e.g. W21X50, HSS6X6X3/8, Pipe4STD
include_inside_facesboolean–Tubes only: add interior surface, as hot-dip galvanizing coats vented HSS/pipe interiors. Default false (outside only).
length_ftnumber–Optional length in feet for a piece/lot area
qtyinteger–Optional piece count (default 1) when a length is given

No output schema declared.

No examples provided.

steel_connection_reference ~100

Describe a structural steel connection type (behaviour, use, what goes wrong) by name, alias or slug — or look up a structural bolt grade (A325, A490, A307). Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
name_or_slugstringyesConnection name, alias or slug (e.g. "clip angle", "base-plate") or a bolt grade (e.g. "A490")

No output schema declared.

No examples provided.

steel_gauge_thickness ~90

Look up sheet steel gauge thickness (gauges 3-28) in inches and mm with lb/ft², for plain, galvanized or stainless series. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
gaugeintegeryesSheet steel gauge number, 3 through 28
materialstring–Gauge series — the same number is a different thickness each

No output schema declared.

No examples provided.

steel_mtr_check ~109

Screen a mill cert's yield and tensile against the specified limits for A992, A572 Gr. 50 or A36 — a screening aid, not acceptance. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
gradestringyesSteel grade: "A992", "A572 Gr. 50" or "A36"
tensile_ksinumberyesReported tensile, ksi
yield_ksinumberyesReported yield, ksi

No output schema declared.

No examples provided.

steel_ncr_generate ~396

Generate a formal Nonconformance Report PDF: identification, description, the violated requirement, containment, root cause (prose or 5-Whys chain), disposition (accept-as-is/repair/rework/reject) with actions, and blank quality-review and sign-off blocks. Flags accept-as-is dispositions whose corrective action describes physical work. The disposition decision belongs to the responsible quality authority. Returns a download link that expires within ~48 hours. Nothing you submit is stored.

NameTypeReqDescription
company_locationstring––
company_namestringyesContractor raising the NCR — appears in the header
containmentstring–What was done on the spot — quarantine, stop work, tag
corrective_actionstring–Bringing this instance into compliance
datestringyesDate raised
descriptionstringyesWhat was found, measured against what was required
locationstring–Area, level, grid, or piece mark
ncr_numberstringyesNCR number from the project register, e.g. "NCR-008"
preventive_actionstring–Stopping recurrence — procedure, inspection, supplier
project_namestringyes–
project_numberstring––
raised_bystringyesName — role
requirement_violatedstringyesThe cited requirement — spec section, drawing/detail, or code clause. An NCR without a cited requirement is dispute fuel.
resolutionstringyesDisposition: accept-as-is (no physical work), repair, rework, or reject
resolution_justificationstring–Required in practice for accept-as-is — the concession basis
root_causestring––
root_cause_whysarray–5-Whys chain, first why to root; overrides root_cause
trade_or_supplierstring––

No output schema declared.

No examples provided.

steel_pdf_markup ~252

Add real Bluebeam-compatible annotation objects to a drawing PDF — counts, length/area measurements with live scales, RFI clouds, callouts — from a markups JSON you supply plus placement coordinates. Pass the PDF as an https URL or small base64; returns a marked PDF download link that expires within ~48 hours. Markups appear in Bluebeam Revu's Markups List. You decide placement; the tool guarantees the format. Nothing you submit is stored.

NameTypeReqDescription
authorstring–Markups List author column
coordinate_spacestring––
markupsarrayyesMarkups to place — geometry in ratio (0–1 from top-left) or pdf coordinates
page_scalesobject–Per-page scale overrides, keyed by page number string
pdf_base64string–Base64 PDF for small files (~3 MB max decoded); prefer pdf_url for drawing sets
pdf_urlstring–HTTPS URL of the source drawing PDF (fetched server-side, SSRF-guarded)
scalestring–Document scale for measurements, e.g. "1/4 in = 1 ft" or "1:100"

No output schema declared.

No examples provided.

steel_pipe_schedule ~137

Steel pipe dimensions by NPS and schedule: OD, wall, inside diameter and lb/ft for schedules 5, 10, 40/STD, 80/XS, 160 and XXS. Omit the schedule to list them all. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
npsstringyesNominal pipe size, e.g. "2", "1/2", "1-1/4"
schedulestring–Optional schedule: "40", "80", "160", "STD", "XS", "XXS", "5", "10"

No output schema declared.

No examples provided.

steel_plate_weight ~139

Compute carbon steel plate weight from thickness (decimal or fraction) and width/length in inches, with optional material cost via price_per_lb. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
length_innumberyesPlate length in INCHES
price_per_lbnumber–Optional material price in $/lb, to include a cost estimate
thickness_in–yesPlate thickness in inches — decimal or fraction ("3/4", "1-1/8")
width_innumberyesPlate width in INCHES (a 4x8 ft plate is 48 x 96 in)

No output schema declared.

No examples provided.

steel_rfi_generate ~325

Generate a formal Request for Information PDF from structured fields — header, meta grid, subject, description, proposed solution, attachments, and a blank response block for the design team. You do the judgement (one issue per RFI, exact drawing references, a proposed path forward); the tool guarantees the format. Returns a download link that expires within ~48 hours. Nothing you submit is stored.

NameTypeReqDescription
attachmentsarray––
company_locationstring––
company_namestringyesContractor issuing the RFI — appears in the header
datestringyesSubmission date
descriptionstringyesThe issue: specific references, what is missing or conflicting, why it matters. Newlines respected.
drawing_refsarray–Exact drawing numbers with revisions
project_namestringyes–
project_numberstring––
proposed_solutionstring–Suggested path forward, framed as a proposal
reasonstring–Category: Design Omission, Design Error, Constructability Issue, Scope Clarification, Site Condition, Missing Information, Coordination Conflict — or free text
response_needed_bystring––
rfi_numberstringyesRFI number from the project register, e.g. "RFI-017"
spec_refsarray––
subjectstringyesOne-line subject — one issue per RFI
submitted_bystringyesName — company
submitted_tostringyesThe party who must respond — engineer, architect, GC

No output schema declared.

No examples provided.

steel_rfq_generate ~209

Generate a vendor-ready Request for Quotation (.xlsx) from structured takeoff line items — grouped by material, with vendor pricing columns, totals and standard terms. You pass parsed line items and a company name; returns a download link that expires within ~48 hours. Nothing you submit is stored.

NameTypeReqDescription
company_locationstring–City, state under the company name, e.g. "Denver, CO"
company_namestringyesBuyer company on the RFQ header and terms — required
date_issuedstring–Free-form issue date; a blank line is used if omitted
line_itemsarrayyesParsed takeoff line items — the calling agent reads the estimate
nesting_rowsarray–Optional fabricator-facing nesting/drop reference rows
project_locationstring––
project_namestringyesProject name for the header and filename
termsarray–Override the eight default terms; omit for the standard set

No output schema declared.

No examples provided.

steel_section_weight ~183

Weight of round bar, square bar, flat bar or round tube from dimensions in inches — lb/ft and optional piece weight, in carbon, stainless or aluminum. For AISC designations use steel_shape_weight; for plate use steel_plate_weight. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
dim1_innumberyesFirst dimension in inches: diameter (round bar), side (square bar), width (flat bar) or OD (round tube)
dim2_innumber–Second dimension in inches: thickness (flat bar) or wall (round tube); unused for round and square bar
length_ftnumber–Optional length in feet for a piece weight
materialstring–Default carbon steel; stainless is +2%, aluminum ×0.35
sectionstringyesCross-section type

No output schema declared.

No examples provided.

steel_shape_weight ~132

Look up an AISC shape designation (W, C, MC, L, HSS, PIPE) for lb/ft, depth and area, with optional piece weight. 14th-Edition-era data. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
designationstringyesAISC designation, e.g. "W21X50", "HSS6X6X3/8", "L4X4X3/8"
length_ftnumber–Optional piece length in feet, for a piece weight
qtyinteger–Optional piece count

No output schema declared.

No examples provided.

steel_takeoff_weight ~101

Roll a member list (AISC designation, length in feet, piece count — up to 500 lines) into a bill-of-steel ledger: weight per line, total pounds and tons, piece and lineal-foot counts. Net weight only; unmatched designations are listed, not guessed. Published nominal values for estimating and orientation, not design guidance.

NameTypeReqDescription
membersarrayyesThe member list to roll up, one line per mark/size

No output schema declared.

No examples provided.

Common questions

What is the ai.structupath/steel-tools MCP server?

ai.structupath/steel-tools is an MCP server listed in the public MCP registry as ai.structupath/steel-tools. Steel takeoff, weight and gauge calculators plus RFQ, RFI, NCR and Bluebeam markup generators. This page covers its hosted endpoint (https://www.structupath.ai/api/mcp).

Is the ai.structupath/steel-tools MCP server safe to use?

ai.structupath/steel-tools scores 78 out of 100 on VerifyMCP. 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 ai.structupath/steel-tools MCP server expose?

ai.structupath/steel-tools exposes 14 tools: steel_gauge_thickness, steel_plate_weight, steel_shape_weight, steel_connection_reference, steel_bolt_pretension, and 9 more. Their descriptions and schemas cost roughly 2,470 tokens of context every time the server is loaded.

Does the ai.structupath/steel-tools MCP server require authentication?

No. We connected to ai.structupath/steel-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.structupath/steel-tools MCP server still maintained?

ai.structupath/steel-tools is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.