# Lexington (remote · mcp.lexingtonthemes.com)

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

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.lexingtonthemes.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp.md), [page](https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp)

## Channel facts

- Endpoint: `https://mcp.lexingtonthemes.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 665 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http com-lexingtonthemes-lexington 'https://mcp.lexingtonthemes.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-lexingtonthemes-lexington": {
      "url": "https://mcp.lexingtonthemes.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-lexingtonthemes-lexington": {
      "type": "http",
      "url": "https://mcp.lexingtonthemes.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-lexingtonthemes-lexington]
url = "https://mcp.lexingtonthemes.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lexingtonthemes-lexington": {
      "type": "remote",
      "url": "https://mcp.lexingtonthemes.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-lexingtonthemes-lexington --url 'https://mcp.lexingtonthemes.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lexingtonthemes-lexington:
    url: "https://mcp.lexingtonthemes.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-lexingtonthemes-lexington": {
      "Transport": "http",
      "Url": "https://mcp.lexingtonthemes.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lexingtonthemes-lexington -t streamable-http -u 'https://mcp.lexingtonthemes.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-lexingtonthemes-lexington": {
      "type": "http",
      "url": "https://mcp.lexingtonthemes.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, +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.

### 2026-11-18 (score 64, +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.

### 2026-11-16 (score 63, +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.

### 2026-11-14 (score 62, +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.

### 2026-11-12 (score 61, +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.

### 2026-11-10 (score 60, +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.

### 2026-11-08 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 58)

First indexed and scored.

## MCP tools (7)

### `get_guidelines` (~36 tokens)

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

### `list_themes` (~39 tokens)

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

### `search_sections` (~125 tokens)

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

Input parameters:

- `group` (string): Section group: heros, features, pricing, ctas, faqs, testimonials, landing
- `include_parts` (boolean): Also return cards that take props (kind: part). Default false.
- `mode` (string): Only themes with this colour mode
- `query` (string): Words like 'hero split screenshot', 'pricing two tiers', 'faq'
- `theme` (string): Theme slug to restrict to

### `get_theme_setup` (~48 tokens)

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.

Input parameters:

- `theme` (string, required)

### `get_design` (~89 tokens)

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.

Input parameters:

- `theme` (string, required)

### `get_skill` (~137 tokens)

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.

Input parameters:

- `target` (string): Where skills live in this project. cursor: .cursor/skills/ (default). claude: .claude/skills/. agents: one AGENTS.md block to append, for clients without skills.
- `theme` (string, required)

### `get_sections` (~191 tokens)

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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 61
- 2026-11-12: 61
- 2026-11-11: 60
- 2026-11-10: 60
- 2026-11-09: 59
- 2026-11-08: 59
- 2026-11-07: 58

## 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.

## Links

- Remote endpoint: https://mcp.lexingtonthemes.com/mcp
- Website: https://lexingtonthemes.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-lexingtonthemes-lexington/mcp
