Skip to content
anlyon.devby Anlyon

The UI Index

com.theuiindex/screenstheuiindex.comstreamable-httpv1.0.0Scanned

Real website screens for UI inspiration: login, pricing, checkout and more from live sites.

3 tools: 3 only read.

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

Anlyon alternative

Run the operations that matter 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.

3 tools

Only reads 3Show 3 read-only tools
  • get_screenRead one captured screen by its id (from search_screens): site, device, type, sector, state, summary, the interface elements marked on it, a thumbnail and the link to the full scre…No findings

    Why it is in this group

    • The name "get_screen" says "get": a word for reading.
    Description, as the server wrote it
    Read one captured screen by its id (from search_screens): site, device, type, sector, state, summary, the interface elements marked on it, a thumbnail and the link to the full screenshot on theuiindex.com.

    Annotations the server declares

    • title: Get one website screen
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_screen_typesList the screen types (login, pricing, checkout…), sectors (banking, software…) and interface states (form error, empty cart…) The UI Index uses, with how many screens each has.No findings

    Why it is in this group

    • The name "list_screen_types" says "list": a word for reading.
    Description, as the server wrote it
    List the screen types (login, pricing, checkout…), sectors (banking, software…) and interface states (form error, empty cart…) The UI Index uses, with how many screens each has. Use the keys as search_screens filters.

    Annotations the server declares

    • title: List screen types, sectors and states
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_screensFind real examples of website screens captured from live sites: login and sign-up pages, pricing pages, checkouts, carts, search results, home pages, forms with errors and more, on…Reads text others writeNo findings

    Why it is in this group

    • The name "search_screens" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Find real examples of website screens captured from live sites: login and sign-up pages, pricing pages, checkouts, carts, search results, home pages, forms with errors and more, on desktop and mobile, across sectors such as banking, insurance, software, retail and travel. Use it for UI and UX inspiration, design references, competitor research, or "show me how other sites do X". Returns up to 8 screens with a summary, a thumbnail and a link to the full screenshot on theuiindex.com.

    Annotations the server declares

    • title: Search real website screens
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

No check matched anything in these tool definitions. That is not a safety guarantee.

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 screens https://theuiindex.com/mcp
claude mcp add --transport http screens https://theuiindex.com/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": [
      "mcp__screens__search_screens",
      "mcp__screens__get_screen",
      "mcp__screens__list_screen_types"
    ],
    "ask": [],
    "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 screens. Review it before you use it.

Capability tags behind 1 rule
  • mcp__screens__search_screens untrusted-input

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/com.theuiindex/screens/verify?hash=a4f3a21409236f11691d15eb246cc5be8367d47812cb01af6d083ed0a43c2efb" | jq -e '.changed == false'

Pinned hash a4f3a2140923, from Nov 3, 2026, 15:18 UTC.

Watch

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

https://anlyon.dev/servers/com.theuiindex/screens/changes.xml

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

Badge

anlyon.dev badge for com.theuiindex/screens
[![anlyon.dev](https://anlyon.dev/badge/com.theuiindex/screens.svg)](https://anlyon.dev/servers/com.theuiindex/screens)

Source: MCP Registry. Synced Nov 3, 2026, 15:17 UTC.