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/heysash/lemonsqueezy-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/heysash/lemonsqueezy-mcp/lemonsqueezy-mcp)<a href="https://agentmods.dev/mcp/heysash/lemonsqueezy-mcp/lemonsqueezy-mcp"><img src="https://agentmods.dev/badge/mcp/heysash/lemonsqueezy-mcp/lemonsqueezy-mcp/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/heysash/lemonsqueezy-mcp/lemonsqueezy-mcp"><img src="https://agentmods.dev/badge/mcp/heysash/lemonsqueezy-mcp/lemonsqueezy-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lemonsqueezy-mcp 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 10d 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
{ "lemonsqueezy-mcp": { "command": "npx", "args": [ "-y", "@heysash/lemonsqueezy-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.
- 10d ago First seen · 9 lines scan A d88f3c4a3e78
lemonsqueezy-mcp is an MCP server published in the GitHub repository heysash/lemonsqueezy-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-08-31.
Other mcp servers, from other repositories
indie-founder-mcp
MCP server "indie-founder-mcp" as configured in charlie-morrison/indie-founder-mcp. Launched with https://github.com/charlie-morrison/indie-founder-mcp/releases/download/v0.2.0/i. Needs 7 environment variables to run.
robokassa-mcp
Comprehensive Python client and MCP server for Robokassa payment gateway. Runs locally from the robokassa-mcp Python package. Needs 4 environment variables to run.
mcp-server
Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral. Runs locally from the @roamzy/mcp-server npm package. Needs 3 environment variables to run.
investor-relations-mcp
MCP server "investor-relations-mcp" as configured in adelaidasofia/investor-relations-mcp. Launched with https://github.com/adelaidasofia/investor-relations-mcp/releases/download/v0.1.0. Needs 1 environment variable to run.
stripekit
The create-next-app of Stripe. Declarative catalog reconciliation into your own Stripe account, plus correct-by-construction billing code you own. Runs locally from the stripekit npm package.
stripe
Python bindings for the Stripe API. Runs locally from the stripe Python package.