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/vaaya-ai/vaaya-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/vaaya-ai/vaaya-mcp/vaaya)<a href="https://agentmods.dev/mcp/vaaya-ai/vaaya-mcp/vaaya"><img src="https://agentmods.dev/badge/mcp/vaaya-ai/vaaya-mcp/vaaya/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/vaaya-ai/vaaya-mcp/vaaya"><img src="https://agentmods.dev/badge/mcp/vaaya-ai/vaaya-mcp/vaaya.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vaaya 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 11d 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
{
"vaaya": {
"url": "https://vaaya.ai/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.
- 11d ago First seen · 5 lines scan A eafec9dad6af
vaaya is an MCP server published in the GitHub repository vaaya-ai/vaaya-mcp (43 stars, last pushed 7d 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-30.
Other mcp servers, from other repositories
primr
MCP server "primr" as configured in blisspixel/primr. Launched with primr mcp.
verantis-mcp
MCP server for Verantis — the verified directory for machine payments (x402 & MPP). Find live-verified services and check a wallet before your agent pays. Runs locally from the verantis-mcp Python package. Needs 1 environment variable to run.
intelligence-mcp
Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP. Runs locally from the @goodmeta/intelligence-mcp npm package. Needs 2 environment variables to run.
frisk
Screen the counterparty of an x402 payment before an agent pays it. Runs offline by default. Runs locally from the frisk-mcp npm package. Needs 2 environment variables to run.
canton-agent-mcp
MCP server that lets AI agents pay on the Canton Network through a human's mobile wallet: the agent asks, the human approves on their phone, hardware signs. Runs locally from the canton-agent-mcp npm package.
fiatdock
Cash out an AI agent's USDC to a real bank account (non-custodial, licensed provider) — plus first-party Base chain data, token safety, and a marketplace where agents pay each other per call in USDC via x402, auto-paid from your wallet. Runs locally from the fiatdock-mcp npm package. Needs 3 environment variables to…