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/evidai/agent-payment-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/evidai/agent-payment-mcp/alpaca-guard)<a href="https://agentmods.dev/mcp/evidai/agent-payment-mcp/alpaca-guard"><img src="https://agentmods.dev/badge/mcp/evidai/agent-payment-mcp/alpaca-guard/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/evidai/agent-payment-mcp/alpaca-guard"><img src="https://agentmods.dev/badge/mcp/evidai/agent-payment-mcp/alpaca-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alpaca-guard 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
{
"alpaca-guard": {
"command": "npx",
"args": [
"-y",
"alpaca-guard-mcp"
],
"env": {
"ALPACA_API_KEY": "",
"ALPACA_SECRET_KEY": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 13 lines scan A d05db3e88bf2
alpaca-guard is an MCP server published in the GitHub repository evidai/agent-payment-mcp (3 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
mcp-server
Agent payment infrastructure MCP server. Give AI agents autonomous payment capability — stablecoin transfers, currency swaps, agent wallets, and fiat operations on Hedera. Works with Claude, LangChain, CrewAI, AutoGPT. Runs locally from the @bananacrystal/mcp-server npm package.
stipend
Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt. Runs locally from the stipend npm package.
p402
Multi-provider AI router with x402 micropayment settlement on Base L2. 1% flat fee. Runs locally from the @p402/mcp-server npm package. Needs 2 environment variables to run.
onchain-agent-wallets
Give an AI agent a Solana spending allowance instead of your key. Chain-enforced cap, x402. Runs locally from the @three-ws/onchain-agent-wallets npm package. Needs 5 environment variables to run.
agentpay
Budget-capped x402 payments for AI agents: verifiable receipts, trust routing, 17 free tools. Runs locally from the @romudille/agentpay-mcp npm package. Needs 2 environment variables to run.
agentpay
AgentPay — the economic-intelligence layer for AI agents: budget-capped tool calls with verifiable receipts, plus verifiedroute buyer-side x402 trust routing. 17 tools free to start, no keys; set AGENTPAYBASEKEY to settle paid tools in-place (gasless E. Runs locally from the @romudille/agentpay-mcp npm package.