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/nirholas/metaplex-agent-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/nirholas/metaplex-agent-mcp/metaplex-agent)<a href="https://agentmods.dev/mcp/nirholas/metaplex-agent-mcp/metaplex-agent"><img src="https://agentmods.dev/badge/mcp/nirholas/metaplex-agent-mcp/metaplex-agent/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/nirholas/metaplex-agent-mcp/metaplex-agent"><img src="https://agentmods.dev/badge/mcp/nirholas/metaplex-agent-mcp/metaplex-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
metaplex-agent 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 9d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 15 lines scan A 928422fc3184
metaplex-agent is an MCP server published in the GitHub repository nirholas/metaplex-agent-mcp (3 stars, last pushed 2d 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
mainstreet
Reputation oracle for AI agents on Base: SAFE/CAUTION/BLOCK + 0-100 score before you pay. x402+MCP. Remote server at avisradar-production.up.railway.app.
aegis-protocol
Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC. Runs locally from the @aegis-protocol/mcp-server npm package. Needs 4 environment variables to run.
arcbounty-mcp
Put an AI agent to work for USDC: it takes on-chain bounties and is paid into its own wallet. Runs locally from the arcbounty-mcp npm package. Needs 8 environment variables to run.
basebounty-mcp
Put an AI agent to work for USDC on Base: it takes on-chain bounties, paid to its own wallet. Runs locally from the basebounty-mcp npm package. Needs 7 environment variables to run.
erc-8126-scan
378k+ ERC-8004 agents and their security verifications. Two tools free, the rest USDC over x402. Remote server at erc8126scan.ai.
agentstamp
Identity certificates, public registry, and wishing well for AI agents — x402 micropayments on Base. Remote server at agentstamp.org.