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/rsweeting1/pixelvault-mcp/pixelvaultgit clone --depth 1 https://github.com/rsweeting1/pixelvault-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/rsweeting1/pixelvault-mcp/pixelvault)<a href="https://agentmods.dev/mcp/rsweeting1/pixelvault-mcp/pixelvault"><img src="https://agentmods.dev/badge/mcp/rsweeting1/pixelvault-mcp/pixelvault.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pixelvault 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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 10 lines scan A 970b96fd61c6
pixelvault is an MCP server published in the GitHub repository rsweeting1/pixelvault-mcp (0 stars, last pushed 4mo ago), with no licence file. 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
seeany-product-visuals-mcp
Plan and create ecommerce product visuals from WorkBuddy, Codex, Claude Code, Cursor, and other AI agents with SeeAny. Runs locally from the seeany-product-visuals-mcp npm package.
discogs-mcp
Model Context Protocol server for Discogs — search the catalog, manage your collection and wantlist, and work the marketplace from Claude and other MCP clients. Runs locally from the discogs-mcp npm package. Needs 2 environment variables to run.
shopify-mcp
MCP server for Shopify Admin API with a ComfyUI bridge for AI product image generation. Runs locally from the @miller-joe/shopify-mcp npm package. Needs 6 environment variables to run.
vips
Creator economy platform for agents: posts, paid content, subscriptions, streams. 1% fee. Runs locally from the vipsallowed npm package. Needs 2 environment variables to run.
tryonfy-mcp-server
MCP server for TryOnfy - AI virtual try-on platform for clothes, hairstyles, and accessories. Runs locally from the tryonfy-mcp-server npm package.
lsp
Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language. Remote server at lightsyncpro.com.