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/ahmaddioxide/image-resolver-mcp/image-resolvergit clone --depth 1 https://github.com/ahmaddioxide/image-resolver-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/ahmaddioxide/image-resolver-mcp/image-resolver)<a href="https://agentmods.dev/mcp/ahmaddioxide/image-resolver-mcp/image-resolver"><img src="https://agentmods.dev/badge/mcp/ahmaddioxide/image-resolver-mcp/image-resolver.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
image-resolver 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
{
"image-resolver": {
"command": "npx",
"args": [
"-y",
"@ahmaddioxide/mcp-image-resolver"
],
"env": {
"PEXELS_API_KEY": "",
"UNSPLASH_ACCESS_KEY": ""
}
}
}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 · 13 lines scan A 8b8264830221
image-resolver is an MCP server published in the GitHub repository ahmaddioxide/image-resolver-mcp (0 stars, last pushed 6mo 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
image-search-mcp
MCP server "image-search-mcp" as configured in serbyte-development/image-search-mcp. Runs locally from the serbyte-image-search-mcp Python package. Needs 3 environment variables to run.
spotify-mcp-server
The most complete Spotify MCP: playback, library, playlists, search, podcasts and audiobooks. Runs locally from the @novalux12/spotify-mcp npm package. Needs 1 environment variable to run.
pexafy-mcp
Semantic search over free-to-use stock photos from 9 libraries: by words, image, or similar. Remote server at mcp.pexafy.com.
unsplash
MCP server "unsplash", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-unsplash.
pexels
MCP server "pexels", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-pexels.
mcp-server
MCP server for the FFmpeg Micro video transcoding API — create, monitor, download transcodes. Runs locally from the @ffmpeg-micro/mcp-server npm package. Needs 1 environment variable to run.