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/lacryptorina/vedetta-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/lacryptorina/vedetta-mcp/vedetta)<a href="https://agentmods.dev/mcp/lacryptorina/vedetta-mcp/vedetta"><img src="https://agentmods.dev/badge/mcp/lacryptorina/vedetta-mcp/vedetta/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/lacryptorina/vedetta-mcp/vedetta"><img src="https://agentmods.dev/badge/mcp/lacryptorina/vedetta-mcp/vedetta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vedetta 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
{
"vedetta": {
"command": "npx",
"args": [
"-y",
"vedetta-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "",
"VEDETTA_API_URL": "",
"VEDETTA_MAX_PRICE_USD": ""
}
}
}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 cd4068daa052
vedetta is an MCP server published in the GitHub repository lacryptorina/vedetta-mcp (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
x402-data-gateway
Twelve x402 tools for data, audits, Morpho decisions, and opportunity preflight on Base. Remote server at agents.samedaydesk.com.
fiatdock
A marketplace where AI agents discover MCP services and buy them from other agents per call in USDC via x402, auto-paid from your wallet — plus a non-custodial USDC-to-bank cash-out (licensed provider), first-party Base chain data and token safety. Runs locally from the fiatdock-mcp npm package. Needs 3 environment…
thebuyside-x402-agent
Buyer-side MCP gateway for x402 and MPP (pay.sh) — let any agent pay any metered API on Base or Solana without seeing a 402 or a wallet. Runs locally from the thebuyside-x402-agent npm package.
base-defi
Base chain DeFi yields — Aerodrome, Moonwell, APY, TVL, risk scores. x402. Remote server at base-defi.api.klymax402.com.
defi-yields
Best DeFi yields by token — APY, TVL, risk, protocol. DeFiLlama-powered. x402. Remote server at defi-yields.api.klymax402.com.
solana-launches
New Solana token launches — pump.fun, Raydium, PumpSwap. Price, liquidity, volume. x402. Remote server at solana-launches.api.klymax402.com.