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/theYahia/cloudpayments-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/theyahia/cloudpayments-mcp/cloudpayments)<a href="https://agentmods.dev/mcp/theyahia/cloudpayments-mcp/cloudpayments"><img src="https://agentmods.dev/badge/mcp/theyahia/cloudpayments-mcp/cloudpayments.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cloudpayments 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 6d 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
{
"cloudpayments": {
"command": "npx",
"args": [
"-y",
"@theyahia/cloudpayments-mcp"
],
"env": {
"CLOUDPAYMENTS_PUBLIC_ID": "<YOUR_PUBLIC_ID>",
"CLOUDPAYMENTS_API_SECRET": "<YOUR_API_SECRET>"
}
}
}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.
- 6d ago First seen · 13 lines scan A f9200fd70bec
cloudpayments is an MCP server published in the GitHub repository theYahia/cloudpayments-mcp (0 stars, last pushed 5mo 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
blockrun-mcp
Live data for AI agents: search, research, markets, crypto, X/Twitter. Pay per call. Runs locally from the @blockrun/mcp npm package. Needs 1 environment variable to run.
fred-mcp-server
Federal Reserve Economic Data (FRED) MCP Server - Access all 800,000+ economic time series. Runs locally from the fred-mcp-server npm package. Needs 1 environment variable to run.
mcp-aktools
MCP Server for stock and crypto. Runs locally from the mcp-aktools Python package.
sber-mcp
MCP server for Sberbank API — accounts, statements. Bearer token auth. Runs locally from the @theyahia/sber-mcp npm package. Needs 1 environment variable to run.
crypto-prices
Live USD crypto spot prices by ticker (BTC, ETH, SOL, …) for AI agents. x402 pay-per-call. Remote server at api.agishub.com.
cbr-mcp
MCP server for Central Bank of Russia API — currency rates, key rate, precious metals, conversion. Runs locally from the @theyahia/cbr-mcp npm package. Needs 1 environment variable to run.