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/Blyawon/tokensStudioMCPWrote 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/blyawon/tokensstudiomcp/tokens-studio-mcp)<a href="https://agentmods.dev/mcp/blyawon/tokensstudiomcp/tokens-studio-mcp"><img src="https://agentmods.dev/badge/mcp/blyawon/tokensstudiomcp/tokens-studio-mcp/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/blyawon/tokensstudiomcp/tokens-studio-mcp"><img src="https://agentmods.dev/badge/mcp/blyawon/tokensstudiomcp/tokens-studio-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tokens-studio-mcp 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 11d 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
{ "tokens-studio-mcp": { "command": "npx", "args": [ "-y", "tokens-studio-mcp" ] } }
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.
- 11d ago First seen · 9 lines scan A 05d9b212f760
tokens-studio-mcp is an MCP server published in the GitHub repository Blyawon/tokensStudioMCP (4 stars, last pushed 3mo 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
memoire
MCP server "memoire" as configured in memi-design/memi. Launched with memi --profile locked mcp start --no-figma.
memi
Memi is the design layer for agentic AI. Runs locally from the @memi-design/cli npm package.
colors-le
Extract colors from stylesheets and code, with their notation and position. Runs locally from the colors-le-mcp npm package.
design-token-bridge-mcp
Translate design tokens between Tailwind, Figma, CSS, Material 3, and SwiftUI. Runs locally from the design-token-bridge-mcp npm package.
token-reconciler
Find where your design-token sources disagree. Point it at a Figma export and a live-site scan (any DTCG files) and it shows you exactly which tokens have drifted, how much it matters, and gives you a clean diff to act on. Runs locally from the token-reconciler npm package.
kiyas
AI design fidelity — compare Figma designs or screenshots against rendered UI. No API keys. Runs locally from the kiyas-cli npm package. Needs 1 environment variable to run.