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.
npx agentmods add mcp/crossi-dev/velora-mcp/veloragit clone --depth 1 https://github.com/crossi-dev/velora-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/crossi-dev/velora-mcp/velora)<a href="https://agentmods.dev/mcp/crossi-dev/velora-mcp/velora"><img src="https://agentmods.dev/badge/mcp/crossi-dev/velora-mcp/velora.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
velora 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 3d 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
{
"velora": {
"url": "https://tools.somosvelora.com/api/mcp",
"type": "streamable-http"
}
}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.
- 3d ago First seen · 6 lines scan A 55bf84e05923
velora is an MCP server published in the GitHub repository crossi-dev/velora-mcp (0 stars, last pushed 27d 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-adyen
MCP server for Adyen Checkout API v71 — enterprise payments (iFood, Uber, Spotify in LatAm). Runs locally from the @codespar/mcp-adyen npm package. Needs 4 environment variables to run.
mcp-stripe
MCP server for Stripe — global payments API (PaymentIntents, Checkout, Billing, Refunds). Runs locally from the @codespar/mcp-stripe npm package. Needs 2 environment variables to run.
mcp-mercado-pago
Mercado Pago — payments, checkout, PIX, refunds for LATAM. Runs locally from the @codespar/mcp-mercado-pago npm package. Needs 1 environment variable to run.
mcp-stripe-acp
Stripe ACP — AI agent checkout, payment delegation, products, invoices. Runs locally from the @codespar/mcp-stripe-acp npm package. Needs 1 environment variable to run.
mcp
Argentine business automation: Mercado Pago, AFIP/ARCA, WhatsApp, banking, shipping (7 packages). Runs locally from the @ar-agents/mcp npm package. Needs 6 environment variables to run.
paypay-mcp
PayPay QR payments for AI agents: QR codes, status, refunds, cancels. Bilingual JP/EN. Runs locally from the paypay-mcp npm package.