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/rafaelcg/stripekitWrote 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/rafaelcg/stripekit/stripekit)<a href="https://agentmods.dev/mcp/rafaelcg/stripekit/stripekit"><img src="https://agentmods.dev/badge/mcp/rafaelcg/stripekit/stripekit/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/rafaelcg/stripekit/stripekit"><img src="https://agentmods.dev/badge/mcp/rafaelcg/stripekit/stripekit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stripekit 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
{
"stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit@latest",
"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 · 10 lines scan A fbe93264698f
stripekit is an MCP server published in the GitHub repository rafaelcg/stripekit (2 stars, last pushed 2mo 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
labellevie-mcp
MCP server "labellevie-mcp" as configured in McCANNParis/MCPServerLaBelleVie. Runs locally from the labellevie-mcp npm package.
mcp-server
A Model Context Protocol (MCP) server that exposes the flexprice API as tools for AI assistants (e.g. Claude, Cursor, VS Code, Windsurf). Use it to manage customers, plans, prices, subscriptions, invoices, payments, events, and more from your IDE or CLI. Runs locally from the @flexprice/mcp-server npm package.
stripe-mcp
A production-grade Model Context Protocol server for the Stripe API. Runs locally from the stripe-mcp npm package.
lemonsqueezy-mcp
A Model Context Protocol (MCP) server for Lemon Squeezy — 44 audited tools over the official SDK, security-first. Works with any Lemon Squeezy account. Runs locally from the @heysash/lemonsqueezy-mcp npm package.
clawpay
Open-source AI Shopping Agent — AI buys products online using Lithic virtual cards via MCP. Runs locally from the @xodn348/clawpay npm package.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.