Koskamo

Iron/Out MCP

An official MCP server by Iron/Out that provides read-only access to UX Score and Core Web Vitals (TTFB, FCP, LCP, INP, CLS) derived from real-user CrUX data. It exposes two tools: run_ux_benchmark for single-site analysis and compare_sites for side-by-side comparison of up to five websites, returning metrics and report links.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Iron/Out MCP logo, by Iron/OutVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-02Operated by Iron/Out
MCP endpoint (Streamable HTTP)
https://www.iron-out.io/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to iron-out.io ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve UX Score and Web Vitals for a specific website
  • Compare performance metrics across multiple competitor sites
  • Access real-user Chrome data for performance auditing

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
iron-out-ux-score 1.0.0
MCP protocol negotiated in check
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Iron/Out scores how fast and user-friendly a website is for real visitors. Scores come from the Chrome UX Report (CrUX): real Chrome users over the last 28 days, phone traffic, 75th percentile. The UX Score (0 to 100) is built on five Web Vitals: TTFB, FCP, LCP, INP and CLS. No lab test or Lighthouse run happens, and the site is never loaded. Sites with too little Chrome traffic have no score; that says nothing about their speed. Quote the score, the weakest metric and the data period, and always give the user the report link. Only pass monthlyRevenue if the user stated it.

Tools

2 advertised

run_ux_benchmark — Run UX benchmark
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Returns the Iron/Out UX Score (0 to 100) for one website, using real-user Chrome UX Report (CrUX) data from the last 28 days. The score is built on five Web Vitals: TTFB (10%), FCP (15%), LCP (25%), INP (25%) and CLS (25%). Use this when the user asks how fast or user-friendly a site is for real visitors. It does not run a lab test or Lighthouse and does not load the site. Sites with too little Chrome traffic have no CrUX data and return no score. If a monthly revenue band is given, it also estimates the revenue at stake. Returns a summary and a link to the full report.

run_ux_benchmark input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Website or page to check, for example zalando.nl or https://www.example.com/. Use the shop domain visitors actually use (for example www2.hm.com)."
    },
    "language": {
      "enum": [
        "en",
        "nl"
      ],
      "type": "string",
      "description": "Language of the linked report. Use nl when the user writes in Dutch."
    },
    "monthlyRevenue": {
      "enum": [
        "Under €500k",
        "€500k to €2M",
        "€2M to €10M",
        "Over €10M"
      ],
      "type": "string",
      "description": "The site's monthly online revenue band. Only set this if the user said it. Never guess it."
    }
  }
}
run_ux_benchmark annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}
compare_sites — Compare sites
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Compares the Iron/Out UX Score of 2 to 5 websites side by side, using real-user Chrome UX Report (CrUX) data from the last 28 days (Web Vitals: TTFB, FCP, LCP, INP, CLS). Use this for competitor or sector comparisons. It runs no lab test or Lighthouse. Returns a ranking and a link to the full comparison.

compare_sites input schema
{
  "type": "object",
  "required": [
    "urls"
  ],
  "properties": {
    "urls": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 2,
      "description": "The websites to compare, for example [\"zalando.nl\", \"wehkamp.nl\"]."
    },
    "category": {
      "type": "string",
      "description": "Sector label shown in the report, for example Electronics. It does not change the scores."
    },
    "language": {
      "enum": [
        "en",
        "nl"
      ],
      "type": "string",
      "description": "Language of the linked report. Use nl when the user writes in Dutch."
    }
  }
}
compare_sites annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-02: 3 of 3 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
714 ms
95th percentile latency
714 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 714 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http iron-out-mcp https://www.iron-out.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add iron-out-mcp --url https://www.iron-out.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable iron-out-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "iron-out-mcp": {
      "url": "https://www.iron-out.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "iron-out-mcp": {
      "type": "streamableHttp",
      "url": "https://www.iron-out.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start iron-out-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "iron-out-mcp": {
      "type": "http",
      "url": "https://www.iron-out.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http iron-out-mcp https://www.iron-out.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "iron-out-mcp": {
      "url": "https://www.iron-out.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "iron-out-mcp": {
      "serverUrl": "https://www.iron-out.io/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Iron/Out MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Iron/Out MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing