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.
npx agentmods add mcp/igniteui/igniteui-theming/igniteui-theminggit clone --depth 1 https://github.com/IgniteUI/igniteui-themingWrote 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/igniteui/igniteui-theming/igniteui-theming)<a href="https://agentmods.dev/mcp/igniteui/igniteui-theming/igniteui-theming"><img src="https://agentmods.dev/badge/mcp/igniteui/igniteui-theming/igniteui-theming.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
igniteui-theming 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 4d 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
{
"igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
],
"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.
- 4d ago First seen · 10 lines scan A d1cb2e67c219
igniteui-theming is an MCP server published in the GitHub repository IgniteUI/igniteui-theming (44 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
css-sota-mcp
What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data. Remote server at css-sota-mcp.lusrodri.workers.dev.
layout-doctor-mcp
MCP server "layout-doctor-mcp" as configured in h-kazuki-pixel/layout-doctor-mcp. Runs locally from the layout-doctor-mcp npm package.
motionprompts-mcp
MCP server over a catalog of 236 production-grade GSAP motion components: search by design brief, plan a page's information architecture, and fetch copy-pasteable build prompts. Runs locally from the motionprompts-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.