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/iofold/artifact-useWrote 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/iofold/artifact-use/artifact-use-artifact-use)<a href="https://agentmods.dev/mcp/iofold/artifact-use/artifact-use-artifact-use"><img src="https://agentmods.dev/badge/mcp/iofold/artifact-use/artifact-use-artifact-use.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
artifact-use 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 8d 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
{
"artifact-use": {
"type": "http",
"url": "https://artifacts.iofold.com/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.
- 8d ago First seen · 6 lines scan A daa9a4f302df
artifact-use is an MCP server published in the GitHub repository iofold/artifact-use (4 stars, last pushed today), 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
ref
MCP server "ref", hosted remotely at api.ref.tools, as configured in feniix/pi-extensions. Needs 1 environment variable to run.
oss-autopilot
MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools. Runs locally from the @oss-autopilot/mcp npm package.
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay npm package.
ellmos-clatcher-mcp
Utility MCP server: JSON repair, encoding fixes, conversion, duplicates, batch rename, archives. Runs locally from the ellmos-clatcher-mcp npm package.
mcp
Read any web page as clean Markdown for AI agents: fetch, search, metadata, links. SSRF-safe. Remote server at mcp.vanshul.com.
savepinner
Parse, validate, classify, and normalize Pinterest URLs locally without network requests. Runs locally from the savepinner-mcp npm package.