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/willibrandon/pixel-plugin/asepritegit clone --depth 1 https://github.com/willibrandon/pixel-pluginGrade A, and why
aseprite 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 2d 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
{
"aseprite": {
"command": "${CLAUDE_PLUGIN_ROOT}/bin/pixel-mcp",
"args": [],
"env": {
"PIXEL_MCP_CONFIG": "${HOME}/.config/pixel-mcp/config.json"
},
"disabled": false,
"alwaysAllow": [],
"description": "Pixel MCP Server - Provides pixel art creation, animation, and export capabilities"
}
}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.
- 2d ago First seen · 12 lines scan A 9e8b6d6a1d00
aseprite is an MCP server published in the GitHub repository willibrandon/pixel-plugin (302 stars, last pushed 10mo 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-30.
Other mcp servers, from other repositories
3D-AI-Agent-Avatar
3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers. Runs locally from the @three-ws/avatar-agent npm package. Needs 11 environment variables to run.
metaplex-agent
Deploy AI agents on-chain on Solana with an EIP-8004 identity. Deploy fee funds $THREE buybacks. Runs locally from the @three-ws/metaplex-agent-mcp npm package. Needs 9 environment variables to run.
portfolio-mcp
An agent's trading state — portfolio value, PnL, live balances, trade feed, and signed transfers. Runs locally from the @three-ws/portfolio-mcp npm package. Needs 8 environment variables to run.
three-token-mcp
Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token. Runs locally from the @three-ws/three-token-mcp npm package. Needs 5 environment variables to run.
ibm-watsonx
IBM watsonx.ai MCP by three.ws: chat, text generation, embeddings, and tokenization. Runs locally from the @three-ws/ibm-watsonx-mcp npm package. Needs 7 environment variables to run.
x402-mcp
Self-custodial x402 wallet for AI agents: pay any service in USDC or $THREE from your own key. Runs locally from the @three-ws/x402-mcp npm package. Needs 5 environment variables to run.