# Iron/Out UX Score Benchmark (remote · www.iron-out.io)

UX Score and Web Vitals (TTFB, FCP, LCP, INP, CLS) for any website, from real-user CrUX data.

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

## Components

- remote · `www.iron-out.io`: 81/100 (this document), [markdown](https://verifymcp.io/servers/io-iron-out-ux-benchmark/www.md), [page](https://verifymcp.io/servers/io-iron-out-ux-benchmark/www)

## Channel facts

- Endpoint: `https://www.iron-out.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 549 tokens (~274/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Iron/Out UX Score Benchmark MCP server?

Iron/Out UX Score Benchmark is a hosted endpoint at https://www.iron-out.io/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 io-iron-out-ux-benchmark 'https://www.iron-out.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-iron-out-ux-benchmark": {
      "url": "https://www.iron-out.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-iron-out-ux-benchmark": {
      "type": "http",
      "url": "https://www.iron-out.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-iron-out-ux-benchmark]
url = "https://www.iron-out.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-iron-out-ux-benchmark": {
      "type": "remote",
      "url": "https://www.iron-out.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-iron-out-ux-benchmark --url 'https://www.iron-out.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-iron-out-ux-benchmark:
    url: "https://www.iron-out.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-iron-out-ux-benchmark": {
      "Transport": "http",
      "Url": "https://www.iron-out.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-iron-out-ux-benchmark -t streamable-http -u 'https://www.iron-out.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-iron-out-ux-benchmark": {
      "type": "http",
      "url": "https://www.iron-out.io/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-20 (score 81, +1)

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

### 2026-11-18 (score 80, +1)

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

### 2026-11-16 (score 79, +1)

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

### 2026-11-13 (score 78, +1)

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

### 2026-11-11 (score 77, +1)

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

### 2026-11-09 (score 76, +1)

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

### 2026-11-07 (score 75, +1)

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

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

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

## MCP tools (2)

### `run_ux_benchmark` (~246 tokens)

Run UX benchmark

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.

Input parameters:

- `language` (string): Language of the linked report. Use nl when the user writes in Dutch.
- `monthlyRevenue` (string): The site's monthly online revenue band. Only set this if the user said it. Never guess it.
- `url` (string, required): 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).

### `compare_sites` (~160 tokens)

Compare sites

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.

Input parameters:

- `category` (string): Sector label shown in the report, for example Electronics. It does not change the scores.
- `language` (string): Language of the linked report. Use nl when the user writes in Dutch.
- `urls` (array, required): The websites to compare, for example ["zalando.nl", "wehkamp.nl"].

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-iron-out-ux-benchmark/www#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 78
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 76
- 2026-11-09: 76
- 2026-11-08: 75
- 2026-11-07: 75
- 2026-11-06: 74
- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72

## Common questions

### What is the Iron/Out UX Score Benchmark MCP server?

Iron/Out UX Score Benchmark is an MCP server listed in the public MCP registry as io.iron-out/ux-benchmark. UX Score and Web Vitals (TTFB, FCP, LCP, INP, CLS) for any website, from real-user CrUX data. This page covers its hosted endpoint (https://www.iron-out.io/mcp).

### Is the Iron/Out UX Score Benchmark MCP server safe to use?

Iron/Out UX Score Benchmark scores 81 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 Iron/Out UX Score Benchmark MCP server expose?

Iron/Out UX Score Benchmark exposes 2 tools: run_ux_benchmark, compare_sites. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

### Does the Iron/Out UX Score Benchmark MCP server require authentication?

No. We connected to Iron/Out UX Score Benchmark without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Iron/Out UX Score Benchmark MCP server still maintained?

Iron/Out UX Score Benchmark 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 Iron/Out UX Score Benchmark MCP server?

VerifyMCP ran 13 checks on Iron/Out UX Score Benchmark, 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://www.iron-out.io/mcp
- Website: https://www.iron-out.io/benchmark/
- Changelog RSS feed: https://verifymcp.io/servers/io-iron-out-ux-benchmark/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-iron-out-ux-benchmark/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-iron-out-ux-benchmark/www.json
- HTML version of this page: https://verifymcp.io/servers/io-iron-out-ux-benchmark/www
