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/inflowpayai/inflow-cliInstalling this writes the configuration, not the program: `inflow` has to be on your PATH already, or the server will not start.
Wrote 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/inflowpayai/inflow-cli/inflow)<a href="https://agentmods.dev/mcp/inflowpayai/inflow-cli/inflow"><img src="https://agentmods.dev/badge/mcp/inflowpayai/inflow-cli/inflow/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/inflowpayai/inflow-cli/inflow"><img src="https://agentmods.dev/badge/mcp/inflowpayai/inflow-cli/inflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
inflow 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
{
"inflow": {
"command": "inflow",
"args": [
"--mcp"
]
}
}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 · 8 lines scan A d79c3d2b89d0
inflow is an MCP server published in the GitHub repository inflowpayai/inflow-cli (10 stars, last pushed 2d 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-commerce
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 8 environment variables to run.
x402-commerce-solana
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 7 environment variables to run.
x402-commerce-sandbox
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 4 environment variables to run.
x402-trust-mcp
Trust & reliability data for x402 endpoints before your agent pays them. Runs locally from the x402-trust-mcp npm package. Needs 6 environment variables to run.
onyx-mcp
Ed25519-signed ground-truth oracle — 63 paid x402 tools live on Base mainnet. Remote server at onyx-actions.onrender.com.
402index
MCP server for 402 Index — search 15,000+ paid API endpoints across L402, x402, and MPP protocols with real-time health monitoring. Runs locally from the @402index/mcp-server npm package.