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.

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.

Available components

+3 this week 81 Trust /100

Last scanned (18 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

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 Usability69
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +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.

  • 7 Nov 26 +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.

  • 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
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://www.iron-out.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.iron-out.io CN=YE2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA384 6eb91f6c4369790d8fe68445fda8ea43357
SANs: iron-out.io, staging.iron-out.io, www.iron-out.io
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 www.iron-out.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
iron-out.io. 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=31536000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.iron-out.io/mcp Verified 200
http (plaintext) http://www.iron-out.io/mcp HTTPS enforced 301 https://www.iron-out.io/mcp
MCP tools · 2 exposed · ~406 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
compare_sites ~160

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.

NameTypeReqDescription
categorystring–Sector label shown in the report, for example Electronics. It does not change the scores.
languagestring–Language of the linked report. Use nl when the user writes in Dutch.
urlsarrayyesThe websites to compare, for example ["zalando.nl", "wehkamp.nl"].

No output schema declared.

No examples provided.

run_ux_benchmark ~246

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.

NameTypeReqDescription
languagestring–Language of the linked report. Use nl when the user writes in Dutch.
monthlyRevenuestring–The site's monthly online revenue band. Only set this if the user said it. Never guess it.
urlstringyesWebsite 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).

No output schema declared.

No examples provided.

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.

remote · www.iron-out.io

# add to Claude Code
claude mcp add --transport http io-iron-out-ux-benchmark 'https://www.iron-out.io/mcp'
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.