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/themonagroup/monapay-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/themonagroup/monapay-mcp/monapay)<a href="https://agentmods.dev/mcp/themonagroup/monapay-mcp/monapay"><img src="https://agentmods.dev/badge/mcp/themonagroup/monapay-mcp/monapay/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/themonagroup/monapay-mcp/monapay"><img src="https://agentmods.dev/badge/mcp/themonagroup/monapay-mcp/monapay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
monapay 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
{
"monapay": {
"command": "npx",
"args": [
"-y",
"monapay-mcp"
],
"env": {
"MONAPAY_CLIENT_ID": "${MONAPAY_CLIENT_ID}",
"MONAPAY_CLIENT_SECRET": "${MONAPAY_CLIENT_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.
- 1mo ago First seen · 13 lines scan A 725d1670ef7f
monapay is an MCP server published in the GitHub repository themonagroup/monapay-mcp (0 stars, last pushed 1mo 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-09-20.
Other mcp servers, from other repositories
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
mcp
Cynco Accounting MCP Server — AI-native accounting tools via Model Context Protocol. Runs locally from the @cynco/mcp npm package.
sieve-mcp
From company name to investment decision. Sieve scores startups across 7 dimensions so you know who's worth a meeting. Runs locally from the sieve-mcp Python package. Needs 1 environment variable to run.
unit-converter-mcp
60+ units, live FX, timezones, and date arithmetic for AI agents. Remote server at unit-converter-mcp.atlasword.workers.dev.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 3 environment variables to run.
stockbit-mcp
Indonesian exchange (IDX) via your own Stockbit account: quotes, bandarmology, charts. Unofficial. Runs locally from the stockbit-mcp npm package. Needs 4 environment variables to run.