Is the Lexington MCP server down?

mcp-registry/com.lexingtonthemes/lexington · registry v0.4.1 · server reports v0.4.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 17:04 UTC · handshake 576ms

As of 2026-11-22 17:04 UTC, the Lexington MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
1,022
outages (90d)
0
tools
7

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

Point your MCP client at this streamable-http endpoint: https://mcp.lexingtonthemes.com/mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 2 warning(s) across 7 tool(s); ~1,132 tokens of tool definitions.
Scores higher than 19% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~1,132 tokens per session — lighter than 70% of servers.
77 → 77 since 2026-11-15
no tool-poisoning patterns
Descriptions60
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (3)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_design, get_guidelines, get_sections, get_skill, get_theme_setup and 2 more

3 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_design, get_skill, get_theme_setup

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.lexingtonthemes%2Flexington/fixes

get_design 1 change
{
  "name": "get_design",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "theme"
    ],
    "properties": {
      "theme": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_guidelines 1 change
{
  "name": "get_guidelines",
  "description": "Read this first. How to install, fill and fit Lexington sections into an Astro + Tailwind project, and what not to change.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_sections 1 change
{
  "name": "get_sections",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "ids"
    ],
    "properties": {
      "ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 12,
        "minItems": 1,
        "description": "Section ids from search_sections, in page order, e.g. ['brightlight/hero-1', 'brightlight/faq-1']"
      },
      "have": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Install paths already written in this project; they are omitted from the reply."
      },
      "format": {
        "enum": [
          "astro",
          "tsx",
          "html"
        ],
        "type": "string",
        "description": "astro (default): .astro components with fundations. tsx: React components, no props, classes expanded. html: flat HTML, classes expanded."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.lexingtonthemes/lexington"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.lexingtonthemes/lexington"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fcom.lexingtonthemes%2Flexington.svg)](https://glimind.com/server/mcp-registry%2Fcom.lexingtonthemes%2Flexington?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.lexingtonthemes%2Flexington?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.lexingtonthemes%2Flexington.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0ec4cd1e4dfcc69d…, first seen 2026-11-15, included at leaf 279718 of 384,671. Version history · verify what your client received.

Tools (7)

Compare: most reliable other servers · most reliable knowledge servers · most reliable code servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Lexington MCP server down right now?

As of 2026-11-22 17:04 UTC, the Lexington MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Lexington MCP server provide?

Lexington MCP server advertises 7 tools, including get_design, get_guidelines, get_sections, get_skill, get_theme_setup.

How do I install Lexington MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.lexingtonthemes.com/mcp

Is the Lexington MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lexington MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve