# Gage (remote · buildwithgage.com)

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

- Trust score: 84/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `buildwithgage.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage.md), [page](https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage)

## Channel facts

- Endpoint: `https://buildwithgage.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-buildwithgage-gage 'https://buildwithgage.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-buildwithgage-gage": {
      "url": "https://buildwithgage.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-buildwithgage-gage": {
      "type": "http",
      "url": "https://buildwithgage.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-buildwithgage-gage]
url = "https://buildwithgage.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-buildwithgage-gage": {
      "type": "remote",
      "url": "https://buildwithgage.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-buildwithgage-gage --url 'https://buildwithgage.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-buildwithgage-gage:
    url: "https://buildwithgage.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-buildwithgage-gage": {
      "Transport": "http",
      "Url": "https://buildwithgage.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-buildwithgage-gage -t streamable-http -u 'https://buildwithgage.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-buildwithgage-gage": {
      "type": "http",
      "url": "https://buildwithgage.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-12 (score 84, +1)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 83, +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.

### 2026-11-08 (score 82, +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.

### 2026-11-06 (score 81, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 81, +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.

### 2026-11-03 (score 80, +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.

### 2026-11-01 (score 79, +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.

### 2026-10-30 (score 78, +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.

## MCP tools (3)

### `submit_design_for_quote` (~353 tokens)

Submit a design for a CFS fabrication quote

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.

Input parameters:

- `design` (object, required)
- `options` (object)
- `project` (object, required)

Output parameters:

- `compliance` (object)
- `derivation` (object)
- `feasibility` (object)
- `meta` (object)
- `next_steps` (array)
- `panelization_package`
- `quote`
- `review`
- `status` (string)

### `quote_my_building` (~508 tokens)

Price a building in steel framing

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.

Input parameters:

- `ceiling_height_ft` (number): Ceiling height in feet, the same on every storey. Defaults to 9.
- `doors` (integer): Number of doors to frame. Defaults to one per storey plus one.
- `project_type` (string, required): residential 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_pitch` (string): Roof pitch as "N:12". Defaults to 6:12, or 0:12 for a flat roof.
- `roof_type` (string, required): Roof form. A-frames price as gable.
- `stories` (integer, required): Number of storeys, 1 to 4.
- `total_sqft` (number, required): Total floor area across all storeys, in square feet.
- `windows` (integer): Number of windows. Defaults to about one per 120 sq ft.
- `zip` (string, required): 5-digit US ZIP code of the build site.

### `start_my_project` (~323 tokens)

Start a Gage project

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.

Input parameters:

- `email` (string, required): The person's email address, as they gave it. Their project link is sent here.
- `name` (string, required): The person's name, as they gave it.
- `person_agreed` (boolean, required): True only once the person has agreed to send their details to Gage to start the project.
- `phone` (string): Phone number, if they offered one.
- `project_name` (string): A short name for the project, e.g. "Lakeside cabin".
- `quote_id` (string, required): The quote to build from, from quote_my_building or submit_design_for_quote.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 84
- 2026-11-19: 84
- 2026-11-18: 84
- 2026-11-17: 84
- 2026-11-16: 84
- 2026-11-15: 84
- 2026-11-14: 84
- 2026-11-13: 84
- 2026-11-12: 84
- 2026-11-11: 83
- 2026-11-10: 83
- 2026-11-09: 82
- 2026-11-08: 82
- 2026-11-07: 81
- 2026-11-06: 81
- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74

## 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.

## Links

- Remote endpoint: https://buildwithgage.com/mcp
- Website: https://buildwithgage.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage.json
- HTML version of this page: https://verifymcp.io/servers/com-buildwithgage-gage/buildwithgage
