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/Evozim/m2mcent-sdkWrote 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/evozim/m2mcent-sdk/m2mcent)<a href="https://agentmods.dev/mcp/evozim/m2mcent-sdk/m2mcent"><img src="https://agentmods.dev/badge/mcp/evozim/m2mcent-sdk/m2mcent/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/evozim/m2mcent-sdk/m2mcent"><img src="https://agentmods.dev/badge/mcp/evozim/m2mcent-sdk/m2mcent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
m2mcent 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 1mo 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
{
"m2mcent": {
"command": "npx",
"args": [
"-y",
"m2mcent-sdk"
],
"env": {
"BASE_RPC_URL": "",
"RELAYER_PRIVATE_KEY": "",
"TREASURY_ADDRESS": ""
}
}
}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.
- 1mo ago First seen · 14 lines scan A 2dca5c061587
m2mcent is an MCP server published in the GitHub repository Evozim/m2mcent-sdk (0 stars, last pushed 2mo 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
gblin-treasury-risk-regime
Risk regime + treasury for AI agents on Base: free regime reads, signed attestations, idle USDC. Runs locally from the @gblin-protocol/mcp-server npm package. Needs 1 environment variable to run.
tollbooth
Token swaps and honeypot/rug checks for AI agents on 8 chains, paid per-call in USDC via x402. Runs locally from the tollboothswap-mcp npm package. Needs 2 environment variables to run.
x402-mcp-server
x402 Payment Gateway for AI Agents — enable micropayments between agents using USDC on Solana. Runs locally from the x402-mcp-server Python package.
x402-list-mcp
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume. Runs locally from the x402-list-mcp npm package. Needs 2 environment variables to run.
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
eterna-mcp
No-KYC managed MCP for AI agents: sandboxed TypeScript trading SDK, isolated sub-accounts, futures. Remote server at mcp.eterna.exchange.