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/gmitch215/MyMCPWrote 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/gmitch215/mymcp/stripe)<a href="https://agentmods.dev/mcp/gmitch215/mymcp/stripe"><img src="https://agentmods.dev/badge/mcp/gmitch215/mymcp/stripe/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/gmitch215/mymcp/stripe"><img src="https://agentmods.dev/badge/mcp/gmitch215/mymcp/stripe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stripe 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 2d 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
{
"stripe": {
"type": "http",
"url": "https://mymcp.gmitch215.xyz/stripe/mcp?include=Get*&max=200",
"headers": {
"X-Mcp-Upstream-Authorization": "${STRIPE_SECRET_KEY}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 2d ago First seen · 9 lines scan A 17c16f6742ac
stripe is an MCP server published in the GitHub repository gmitch215/MyMCP (7 stars, last pushed yesterday), licensed MPL-2.0. 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-10.
Other mcp servers, from other repositories
vouch
Check if a counterparty is safe to pay: trust/risk score for AI agents. Scam/phishing screen. Remote server at vouch.futuronoti.workers.dev.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
mcp
Discover, inspect and call ranked external data & tool APIs with unified billing and usage audit. Runs locally from the @qverisai/mcp npm package. Needs 3 environment variables to run.
copilot-money-mcp
Query and manage Copilot Money personal finances — local reads, opt-in GraphQL writes. Runs locally from the copilot-money-mcp npm package.
adyen-mcp-server
MCP server "adyen-mcp-server" as configured in Adyen/adyen-mcp. Runs /workspaces/adyen-mcp/typescript/dist/index.js with node. Needs 1 environment variable to run.
llmkit
AI cost tracking: 11 tools for spend, budgets, and Claude Code + Cursor + Cline costs. Runs locally from the @f3d1/llmkit-mcp-server npm package. Needs 2 environment variables to run.