The UI Index
REMOTE · THEUIINDEX.COM
Real website screens for UI inspiration: login, pricing, checkout and more from live sites.
Available components
Last scanned (8 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 543 tokens (~181/item across 3 items; 3 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 Management7
- Stability observed for 2 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 72
First indexed and scored.
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 5 Nov 2026 · Probed https://theuiindex.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=theuiindex.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 91506d1e74b86b3f1385e51c51187738 |
| SANs: theuiindex.com, www.theuiindex.com, *.www.theuiindex.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of theuiindex.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| theuiindex.com. | 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; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://theuiindex.com/mcp | Verified | 200 | |
| http (plaintext) | http://theuiindex.com/mcp | HTTPS enforced | 301 | https://theuiindex.com/mcp |
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 →
get_screen Get one website screen ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Screen id from search_screens. |
No output schema declared.
No examples provided.
list_screen_types List screen types, sectors and states ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_screens Search real website screens ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device the screen was captured on. |
| language | string | – | Language of the page. |
| offset | integer | – | Skip this many results (for more of the same search). |
| query | string | – | Free words: a site, a brand, a pattern or what the screen does, e.g. "two-factor login", "bol", "annual pricing toggle". |
| sector | string | – | Sector key, e.g. software, ai, developer-tools, banking, insurance, retail, groceries, travel, energy, telecom, government. See list_screen_types. |
| state | string | – | Interface state key, e.g. search-results, search-no-results, filters-applied, menu-open, form-error, cart-populated. See list_screen_types. |
| type | string | – | Screen type key, e.g. home, landing, pricing, login (sign-in and sign-up), checkout, cart, search-results, product-detail, form, contact, help. See list_screen_types. |
No output schema declared.
No examples provided.
How do I install the The UI Index MCP server?
The UI Index is a hosted endpoint at https://theuiindex.com/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 · theuiindex.com
claude mcp add --transport http com-theuiindex-screens 'https://theuiindex.com/mcp'
What is the The UI Index MCP server?
The UI Index is an MCP server listed in the public MCP registry as com.theuiindex/screens. Real website screens for UI inspiration: login, pricing, checkout and more from live sites. This page covers its hosted endpoint (https://theuiindex.com/mcp).
Is the The UI Index MCP server safe to use?
The UI Index scores 73 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 The UI Index MCP server expose?
The UI Index exposes 3 tools: search_screens, get_screen, list_screen_types. Their descriptions and schemas cost roughly 448 tokens of context every time the server is loaded.
Does the The UI Index MCP server require authentication?
No. We connected to The UI Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The UI Index MCP server still maintained?
The UI Index is still listed as active in the MCP registry. We last reached this channel on 5 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 The UI Index MCP server?
VerifyMCP ran 13 checks on The UI Index, 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.