Skip to content
anlyon.devby Anlyon

Iron/Out UX Score Benchmark

io.iron-out/ux-benchmarkiron-out.iostreamable-httpv1.0.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • 1 finding

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • run_ux_benchmarkReturns the Iron/Out UX Score (0 to 100) for one website, using real-user Chrome UX Report (CrUX) data from the last 28 days.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "run_ux_benchmark" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "run_ux_benchmark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "run_ux_benchmark" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • compare_sitesCompares 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).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "compare_sites" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "compare" and "website": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.urls), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnrun_ux_benchmark

    The server marks "run_ux_benchmark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "run_ux_benchmark" says "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ux-benchmark https://www.iron-out.io/mcp
claude mcp add --transport http ux-benchmark https://www.iron-out.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__ux-benchmark__run_ux_benchmark",
      "mcp__ux-benchmark__compare_sites"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ux-benchmark. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ux-benchmark__run_ux_benchmark untrusted-input, outbound
  • mcp__ux-benchmark__compare_sites untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.iron-out/ux-benchmark/verify?hash=a921cae800b68b362764af00aff306a90b43f9876f43aeb3ca13bd1ce14ca76f" | jq -e '.changed == false'

Pinned hash a921cae800b6, from Nov 2, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.iron-out/ux-benchmark/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.iron-out/ux-benchmark
[![anlyon.dev](https://anlyon.dev/badge/io.iron-out/ux-benchmark.svg)](https://anlyon.dev/servers/io.iron-out/ux-benchmark)

Source: MCP Registry. Synced Nov 2, 2026, 14:18 UTC.