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.

Gage

REMOTE · BUILDWITHGAGE.COM

Price a building in light-gauge steel framing and start it with the nearest Gage fabricator.

0 this week 84 Trust /100

Last scanned (20 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Cloud Infrastructure

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1359 tokens (~453/item across 3 items; 3 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 Coverage95
  • 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
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 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.

  • 8 Nov 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.

  • 6 Nov 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
  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

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 21 Nov 2026 · Probed https://buildwithgage.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=buildwithgage.com CN=YR2,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 RSA 2048 SHA256-RSA 5d6678a327d065813bb5757f204bc05a9f3
SANs: buildwithgage.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 buildwithgage.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
buildwithgage.com. No DS 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; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://buildwithgage.com/mcp Verified 200
http (plaintext) http://buildwithgage.com/mcp HTTPS enforced 308 https://buildwithgage.com/mcp
MCP tools · 3 exposed · ~1,184 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
quote_my_building ~508

Price a building in cold-formed steel framing from a plain description, through the Gage fabricator network: what it costs to have the frame fabricated and delivered, and which regional shop would build it. Use this when someone has designed a house, ADU, cabin, garage, workshop or small commercial building (in this conversation or elsewhere) and asks what it would cost to build, how to get it built, or whether it can be framed in steel. For example, "how much to build this 1,900 sq ft one-storey gable house near 84032" -> total_sqft 1900, stories 1, roof_type "gable", zip "84032". Only the size, storeys, roof and build-site ZIP are needed; ask the person for the ZIP if you do not have it. Anything else not given (ceiling heights, windows, doors, wall length, pitch, steel gauge) is filled with stated defaults and listed as assumptions. If you have exact walls and openings, submit_design_for_quote gives a tighter price. The price is the steel frame package: framing steel, engineering and delivery. It is not the whole house (no foundation, finishes or labour on site). The fabricator is named by region until they take the job. When the person wants to go ahead, call start_my_project with the quote id.

NameTypeReqDescription
ceiling_height_ftnumber–Ceiling height in feet, the same on every storey. Defaults to 9.
doorsinteger–Number of doors to frame. Defaults to one per storey plus one.
project_typestringyesresidential for a house, cabin or home; adu for an accessory dwelling unit or backyard cottage; garage for a detached or attached garage, carport building or workshop; commercial for a shop, office o…
roof_pitchstring–Roof pitch as "N:12". Defaults to 6:12, or 0:12 for a flat roof.
roof_typestringyesRoof form. A-frames price as gable.
storiesintegeryesNumber of storeys, 1 to 4.
total_sqftnumberyesTotal floor area across all storeys, in square feet.
windowsinteger–Number of windows. Defaults to about one per 120 sq ft.
zipstringyes5-digit US ZIP code of the build site.

No output schema declared.

No examples provided.

start_my_project ~323

Start a real Gage project from a quote, so the person can get their building fabricated: Gage creates their project with the regional fabricator that priced it and emails them a private link to it. From that page they review the quote, talk to the fabricator and follow the frame to delivery. Nothing is charged by starting a project. Only call this when the person has said they want to go ahead, and only with a name and email address they have given you for this. Ask them first: "Shall I send this to Gage so a fabricator can take it on? I'll need your name and email." Set person_agreed to true only after they say yes. Use the quote_id from quote_my_building or submit_design_for_quote. The link goes to their email only; tell them to look for an email from Gage. How Gage handles their details: https://buildwithgage.com/privacy.

NameTypeReqDescription
emailstringyesThe person's email address, as they gave it. Their project link is sent here.
namestringyesThe person's name, as they gave it.
person_agreedbooleanyesTrue only once the person has agreed to send their details to Gage to start the project.
phonestring–Phone number, if they offered one.
project_namestring–A short name for the project, e.g. "Lakeside cabin".
quote_idstringyesThe quote to build from, from quote_my_building or submit_design_for_quote.

No output schema declared.

No examples provided.

submit_design_for_quote ~353

Submit a building design to Gage and get back a real, buildable cold-formed steel (CFS) framing quote from the Gage fabricator network. Use this when you have generated or been given a floor plan or 3D house model and need to know what it costs to frame in steel, who would fabricate it, and how it breaks into panels. Give it structured geometry (levels, walls as start/end points, openings, roof) plus the build site ZIP and project type. It reduces the model to the quoting engine's inputs, checks whether the design can actually be auto-panelized, and returns: - a structural feasibility flag, - an itemized quote (steel, transport, engineering, subtotal, confidence band, fabricator and lead time), - a downloadable preliminary panelization package (panel count, panel footage and totals; the panel-by-panel schedule goes to the Gage fabricator that takes the job). It refuses rather than guesses. Geometry that is invalid or outside what the engine prices comes back as a structured error; a design that is legible but needs a structural decision (curved walls, a header over 12 ft, a cantilevered storey, tall walls) comes back with status "needs_human_review" and no price. A quote is only ever returned for a design that passed every check. Pricing, tonnage and fabricator routing are computed by Gage API v1, not by this tool. Panelization output is preliminary and unstamped; stamped shop drawings are issued by the assigned fabricator after a quote is accepted.

NameTypeReqDescription
designobjectyes–
optionsobject––
projectobjectyes–
NameTypeReqDescription
complianceobjectyes–
derivationobjectyes–
feasibilityobjectyes–
metaobjectyes–
next_stepsarrayyes–
panelization_package–yes–
quote–yes–
review–yes–
statusstringyes–

No examples provided.

Install

How do I install the Gage MCP server?

Gage is a hosted endpoint at https://buildwithgage.com/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 · buildwithgage.com

# add to Claude Code
claude mcp add --transport http com-buildwithgage-gage 'https://buildwithgage.com/mcp'
Common questions

What is the Gage MCP server?

Gage is an MCP server listed in the public MCP registry as com.buildwithgage/gage. Price a building in light-gauge steel framing and start it with the nearest Gage fabricator. This page covers its hosted endpoint (https://buildwithgage.com/mcp).

Is the Gage MCP server safe to use?

Gage scores 84 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 Gage MCP server expose?

Gage exposes 3 tools: submit_design_for_quote, quote_my_building, start_my_project. Their descriptions and schemas cost roughly 1,184 tokens of context every time the server is loaded.

Does the Gage MCP server require authentication?

No. We connected to Gage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Gage MCP server still maintained?

Gage is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Gage MCP server?

VerifyMCP ran 13 checks on Gage, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.