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/zhanyoulin456/seevin-claude-pluginsWrote 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/zhanyoulin456/seevin-claude-plugins/seevin-core-tdesign-mcp-server)<a href="https://agentmods.dev/mcp/zhanyoulin456/seevin-claude-plugins/seevin-core-tdesign-mcp-server"><img src="https://agentmods.dev/badge/mcp/zhanyoulin456/seevin-claude-plugins/seevin-core-tdesign-mcp-server/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/zhanyoulin456/seevin-claude-plugins/seevin-core-tdesign-mcp-server"><img src="https://agentmods.dev/badge/mcp/zhanyoulin456/seevin-claude-plugins/seevin-core-tdesign-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tdesign-mcp-server 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 12d 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.
What it actually says
{
"tdesign-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tdesign-mcp-server"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 12d ago First seen · 10 lines scan A e3f0c9a699eb
tdesign-mcp-server is an MCP server published in the GitHub repository zhanyoulin456/seevin-claude-plugins (4 stars, last pushed 7mo 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
composer_kit_mcp
A Model Context Protocol (MCP) server for Composer Kit UI components and Celo Composer project creation. Runs locally from the composer_kit_mcp Python package.
figma-dev-tools
Figma Dev Tools MCP Server v1.4.13 - Bridge Figma designs to code with AI-powered token extraction, framework-agnostic structured data, React/Vue/HTML component generation, asset downloads, XSS security protection, smart hierarchy fixing, SVG inline rende. Runs locally from the figma-dev-tools npm package.
low-code-ui-mcp
MCP server "low-code-ui-mcp" as configured in markgregg/mcp. Runs locally from the low-code-ui-mcp Python package.
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.