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/MariuszHenn/tseha-mcpWrote 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/mariuszhenn/tseha-mcp/tseha)<a href="https://agentmods.dev/mcp/mariuszhenn/tseha-mcp/tseha"><img src="https://agentmods.dev/badge/mcp/mariuszhenn/tseha-mcp/tseha/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/mariuszhenn/tseha-mcp/tseha"><img src="https://agentmods.dev/badge/mcp/mariuszhenn/tseha-mcp/tseha.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tseha 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 1mo 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
{
"tseha": {
"url": "https://tseha.io/mcp",
"type": "streamable-http"
}
}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.
- 1mo ago First seen · 6 lines scan A 2969a074e717
tseha is an MCP server published in the GitHub repository MariuszHenn/tseha-mcp (2 stars, last pushed 1mo 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
standby-design-mcp
Generate design systems: OKLCH colors, fluid type scales, spacing, shape, icon and motion tokens. Runs locally from the standby-design-mcp npm package.
stitch-mcp-server
Enterprise-ready MCP Server for Google Stitch SDK - AI-powered UI generation for Claude, Cursor, Cline, and VS Code. Generate beautiful web interfaces from text prompts using Model Context Protocol. Runs locally from the stitch-mcp-server npm package.
mcp
AI-powered design and management for Webflow Sites. Remote server at mcp.webflow.com.
mcp-design-system-extractor
MCP server for Storybook design systems — extract component HTML, styles and metadata. Runs locally from the mcp-design-system-extractor npm package. Needs 3 environment variables to run.
design-system
Simplified MCP server for Storybook design system extraction with component analysis tools. Runs locally from the mcp-design-system-extractor npm package.
zenith
Author, validate, edit, and render deterministic .zen design docs to PNG/PDF. Runs locally from the @zenitheditor/zenith-mcp npm package.