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/KingPeque/coinvoyage-paykitWrote 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/kingpeque/coinvoyage-paykit/coinvoyage)<a href="https://agentmods.dev/mcp/kingpeque/coinvoyage-paykit/coinvoyage"><img src="https://agentmods.dev/badge/mcp/kingpeque/coinvoyage-paykit/coinvoyage/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/kingpeque/coinvoyage-paykit/coinvoyage"><img src="https://agentmods.dev/badge/mcp/kingpeque/coinvoyage-paykit/coinvoyage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
coinvoyage 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 8d 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
{
"coinvoyage": {
"command": "npx",
"args": [
"-y",
"@kingpeque/coinvoyage-mcp"
],
"env": {
"COINVOYAGE_API_KEY": "",
"COINVOYAGE_API_SECRET": "",
"COINVOYAGE_API_BASE_URL": ""
}
}
}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.
- 8d ago First seen · 14 lines scan A 7b39c4b4e239
coinvoyage is an MCP server published in the GitHub repository KingPeque/coinvoyage-paykit (0 stars, last pushed 4mo 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
yolfi-agent
Let AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks. Runs locally from the @yolfi/agent npm package. Needs 2 environment variables to run.
crypto-swap
Native cross-chain swaps: Bitcoin, Ethereum, Solana, Polkadot, Tron, Arbitrum. Quote, swap, track. Remote server at chainflip-broker.io.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
alloc-context
Portfolio-aware crypto context — CEX or wallet holdings, holdings-scoped market, optional allocation analysis. Runs locally from the alloc-context Python package.
btc-node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402. Remote server at mcp.btcnode.uk.
crypto-prices-mcp
Live and historical cryptocurrency prices via CoinGecko free API. Remote server at crypto-prices-mcp.atlasword.workers.dev.