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.

Lexington

REMOTE · MCP.LEXINGTONTHEMES.COM

Finished Tailwind sections and design systems from every Lexington theme, as Astro, React or HTML.

+3 this week 65 Trust /100

Last scanned (15 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

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 Security46
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 665 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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 (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 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.

  • 18 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.

  • 16 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.

  • 14 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.

  • 12 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.

  • 10 Nov 26 +1

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

  • 8 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 58

    First indexed and scored.

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://mcp.lexingtonthemes.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lexingtonthemes.com CN=WE1,O=Google Trust Services,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA256 64f515823006c6b5137766b67c7a075c
SANs: lexingtonthemes.com, mcp.lexingtonthemes.com, *.mcp.lexingtonthemes.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 mcp.lexingtonthemes.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
lexingtonthemes.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.lexingtonthemes.com/mcp Verified 200
http (plaintext) http://mcp.lexingtonthemes.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~665 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
get_design ~89

The theme's design system: typography recipes, what each colour scale means, spacing rhythm, components, do and don't, plus roles.json (the same as data: action, panel, ink, muted, rule, radius, heading and body recipes, measured from the sections). Read before changing anything visual, reskinning, or aliasing the palette onto a host.

NameTypeReqDescription
themestringyes–

No output schema declared.

No examples provided.

get_guidelines ~36

Read this first. How to install, fill and fit Lexington sections into an Astro + Tailwind project, and what not to change.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sections ~191

One or more sections with every file they need (fundations, icons, placeholder images), each with the path to write it to. Shared files are sent once. Ask for the whole page in one call. format 'tsx' returns React components (Next, Vite, Remix), format 'html' flat HTML with the Tailwind classes expanded (Vue, Svelte, plain HTML). Both are standalone sections only; parts have no flat export.

NameTypeReqDescription
formatstring–astro (default): .astro components with fundations. tsx: React components, no props, classes expanded. html: flat HTML, classes expanded.
havearray–Install paths already written in this project; they are omitted from the reply.
idsarrayyesSection ids from search_sections, in page order, e.g. ['brightlight/hero-1', 'brightlight/faq-1']

No output schema declared.

No examples provided.

get_skill ~137

The companion skill for a theme, to write into the project so the agent keeps the theme's rules on every later edit without calling this server: the theme's own design skill (typography, colour, spacing, components, do and don't) plus the shared Lexington sections skill (fill, fit, reskin, port). Call once per project after the first get_sections.

NameTypeReqDescription
targetstring–Where skills live in this project. cursor: .cursor/skills/ (default). claude: .claude/skills/. agents: one AGENTS.md block to append, for clients without skills.
themestringyes–

No output schema declared.

No examples provided.

get_theme_setup ~48

Once per project, per theme: tokens.css and Fonts.astro to write, plus the two setup steps. Call before the first get_sections for a theme.

NameTypeReqDescription
themestringyes–

No output schema declared.

No examples provided.

list_themes ~39

Every theme available, with who it is for, its visual personality, fonts, light/dark mode and section count. Pick one theme per page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_sections ~125

Find sections by role and description. Returns id, group and a one-line description. Use the ids with get_sections.

NameTypeReqDescription
groupstring–Section group: heros, features, pricing, ctas, faqs, testimonials, landing
include_partsboolean–Also return cards that take props (kind: part). Default false.
modestring–Only themes with this colour mode
querystring–Words like 'hero split screenshot', 'pricing two tiers', 'faq'
themestring–Theme slug to restrict to

No output schema declared.

No examples provided.

Install

How do I install the Lexington MCP server?

Lexington is a hosted endpoint at https://mcp.lexingtonthemes.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 · mcp.lexingtonthemes.com

# add to Claude Code
claude mcp add --transport http com-lexingtonthemes-lexington 'https://mcp.lexingtonthemes.com/mcp'
Common questions

What is the Lexington MCP server?

Lexington is an MCP server listed in the public MCP registry as com.lexingtonthemes/lexington. Finished Tailwind sections and design systems from every Lexington theme, as Astro, React or HTML. This page covers its hosted endpoint (https://mcp.lexingtonthemes.com/mcp).

Is the Lexington MCP server safe to use?

Lexington scores 65 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 Lexington MCP server expose?

Lexington exposes 7 tools: get_guidelines, list_themes, search_sections, get_theme_setup, get_design, and 2 more. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.

Does the Lexington MCP server require authentication?

No. We connected to Lexington without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lexington MCP server still maintained?

Lexington 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 Lexington MCP server?

VerifyMCP ran 11 checks on Lexington, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Lexington: Authorization and HTTPS. 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.