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/ohrytskov/stripe-reporting-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/ohrytskov/stripe-reporting-mcp/stripe-reporting)<a href="https://agentmods.dev/mcp/ohrytskov/stripe-reporting-mcp/stripe-reporting"><img src="https://agentmods.dev/badge/mcp/ohrytskov/stripe-reporting-mcp/stripe-reporting/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/ohrytskov/stripe-reporting-mcp/stripe-reporting"><img src="https://agentmods.dev/badge/mcp/ohrytskov/stripe-reporting-mcp/stripe-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stripe-reporting 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 9d 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-reporting": {
"command": "node",
"args": [
"./node_modules/tsx/dist/cli.mjs",
"src/index.ts"
]
}
}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.
- 9d ago First seen · 9 lines scan A f76083ab5144
stripe-reporting is an MCP server published in the GitHub repository ohrytskov/stripe-reporting-mcp (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
dodopayments
The official TypeScript library for the Dodo Payments API. Runs locally from the dodopayments npm package.
mcp-registry-finder
MCP server "mcp-registry-finder" as configured in bharat3645/mcp-registry-finder. Runs locally from the mcp-registry-finder npm package.
agent-reputation-mcp-server
MCP Server for AI agent trust scores, ratings, and reputation tracking. Runs locally from the @aiagentkarl/agent-reputation-mcp-server npm package.
restaurant-mcp
MCP server "restaurant-mcp" as configured in rick001/restaurant-mcp. Runs locally from the restaurant-mcp npm package.
mcp-server
Model Context Protocol (MCP) server for AI-assisted development of CAP applications. Runs locally from the @cap-js/mcp-server npm package.
d365fo-client
Microsoft Dynamics 365 Finance & Operations client and MCP server. Runs locally from the d365fo-client Python package. Needs 4 environment variables to run.