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.

Steel Brain

REMOTE · API.STEELBRAIN.DEV · 2 COMPONENTS · SCANNED SEP 29

Trade-verified steel grade properties, substitution verdicts, and mill-cert guidance for AI agents.

62 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 Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 206 tokens (~68/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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
Install

How do I install the Steel Brain MCP server?

Steel Brain is a hosted endpoint at https://api.steelbrain.dev/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 · api.steelbrain.dev

# add to Claude Code
claude mcp add --transport http dryow1-steel-brain 'https://api.steelbrain.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dryow1-steel-brain": {
      "url": "https://api.steelbrain.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dryow1-steel-brain": {
      "type": "http",
      "url": "https://api.steelbrain.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dryow1-steel-brain]
url = "https://api.steelbrain.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dryow1-steel-brain": {
      "type": "remote",
      "url": "https://api.steelbrain.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dryow1-steel-brain --url 'https://api.steelbrain.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dryow1-steel-brain:
    url: "https://api.steelbrain.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dryow1-steel-brain": {
      "Transport": "http",
      "Url": "https://api.steelbrain.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dryow1-steel-brain -t streamable-http -u 'https://api.steelbrain.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dryow1-steel-brain": {
      "type": "http",
      "url": "https://api.steelbrain.dev/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
  • 27 Sept 26 +1

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

  • 26 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 61

    First indexed and scored.

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 29 Sept 2026 · Probed https://api.steelbrain.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.steelbrain.dev CN=YE2,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 ECDSA 256 ECDSA-SHA384 5436b0fb6c27bb2446b30586e96b25e630c
SANs: api.steelbrain.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.steelbrain.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
steelbrain.dev. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.steelbrain.dev/mcp Verified 200
http (plaintext) http://api.steelbrain.dev/mcp HTTPS enforced 301 https://api.steelbrain.dev/mcp
MCP tools · 3 exposed · ~168 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
cert_guide ~53

Which mill cert type applies for a grade + use case (e.g. EH36 shipbuilding), and what fields to check on the cert.

NameTypeReqDescription
gradestringyes–
use_casestringyes–

No output schema declared.

No examples provided.

grade_lookup ~52

Look up a steel grade: properties, chemistry, forms, applications, weldability. Aliases accepted (e.g. 4140 = 42CrMo4 = SCM440).

NameTypeReqDescription
gradestringyes–

No output schema declared.

No examples provided.

substitution_check ~63

Check if one steel grade can substitute another for a given application (machined / welded-structural / pressure). Returns verdict + reasoning from verified trade rules.

NameTypeReqDescription
applicationstringyes–
from_gradestringyes–
to_gradestringyes–

No output schema declared.

No examples provided.

Common questions

What is the Steel Brain MCP server?

Steel Brain is an MCP server listed in the public MCP registry as io.github.dryow1/steel-brain. Trade-verified steel grade properties, substitution verdicts, and mill-cert guidance for AI agents. This page covers its hosted endpoint (https://api.steelbrain.dev/mcp).

Is the Steel Brain MCP server safe to use?

Steel Brain scores 62 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 Steel Brain MCP server expose?

Steel Brain exposes 3 tools: grade_lookup, substitution_check, cert_guide. Their descriptions and schemas cost roughly 168 tokens of context every time the server is loaded.

Does the Steel Brain MCP server require authentication?

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

Is the Steel Brain MCP server still maintained?

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