Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/LE-VAI/designesy-orgWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/le-vai/designesy-org/designesy)<a href="https://agentmods.dev/mcp/le-vai/designesy-org/designesy"><img src="https://agentmods.dev/badge/mcp/le-vai/designesy-org/designesy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/le-vai/designesy-org/designesy"><img src="https://agentmods.dev/badge/mcp/le-vai/designesy-org/designesy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
designesy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- designesy-org — 86% identical, 2 lines differ
What it actually says
{
"designesy": {
"command": "uvx",
"args": [
"designesy-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 9 lines scan A 4fbd12e48840
designesy is an MCP server published in the GitHub repository LE-VAI/designesy-org (0 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
dembrandt
Extract design tokens and publicly visible CSS information from any website. Runs locally from the dembrandt npm package.
uxlint
Audit a site's UX the way a design-literate reviewer would, with a concrete fix for every finding. Runs locally from the @uxlint-net/uxlint npm package.
tokens-studio-mcp
MCP server "tokens-studio-mcp" as configured in Blyawon/tokensStudioMCP. Runs locally from the tokens-studio-mcp npm package.
atag-mcp
ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers. Runs locally from the atag-mcp npm package.
accessibility-mcp-server
MCP-Server fuer Web-Accessibility-Checks: WCAG 2.1/2.2 Pruefung, Kontrast, ARIA, Formular-Validierung. Runs locally from the accessibility-mcp-server Python package.
branding-mcp
AI-powered brand identity generation via MCP with design tokens, typography, and logo assets. Runs locally from the @forgespace/branding-mcp npm package.