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/Saraid10/TrustgateWrote 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/saraid10/trustgate/mcp-payment-safety-testbed)<a href="https://agentmods.dev/mcp/saraid10/trustgate/mcp-payment-safety-testbed"><img src="https://agentmods.dev/badge/mcp/saraid10/trustgate/mcp-payment-safety-testbed/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/saraid10/trustgate/mcp-payment-safety-testbed"><img src="https://agentmods.dev/badge/mcp/saraid10/trustgate/mcp-payment-safety-testbed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-payment-safety-testbed 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
{ "mcp-payment-safety-testbed": { "command": "uvx", "args": [ "mcp-payment-safety-testbed" ] } }
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 9c39815d7a39
mcp-payment-safety-testbed is an MCP server published in the GitHub repository Saraid10/Trustgate (3 stars, last pushed 1mo ago), licensed Apache-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-08-31.
Other mcp servers, from other repositories
robosystems
Accounting knowledge graphs: SEC XBRL filings, QuickBooks ledgers, reports and forecasts over MCP. Remote server at api.robosystems.ai.
bitcoin-risk-brief
Daily Bitcoin risk with freshness state on every response. Research context, not advice. Runs locally from the @akarazhev/bitcoin-risk-brief-mcp npm package. Needs 1 environment variable to run.
open-paper-trading-mcp
MCP server "open-paper-trading-mcp" as configured in Open-Agent-Tools/open-paper-trading-mcp. Runs locally from the open-paper-trading-mcp Python package.
unified-pay-cli
Unified Payment Gateway CLI & MCP Bridge for Stripe, Razorpay and more. Runs locally from the unified-pay-cli npm package.
expense-budget-tracker
Track expenses, budgets, balances, transfers, and multi-currency reports with OAuth-secured tools. Remote server at mcp.expense-budget-tracker.com.
x402-list-mcp
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume. Runs locally from the x402-list-mcp npm package. Needs 2 environment variables to run.