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.
npx agentmods add mcp/thefraudfather/flint-plugin/agent-transaction-controlgit clone --depth 1 https://github.com/thefraudfather/flint-pluginWrote 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/thefraudfather/flint-plugin/agent-transaction-control)<a href="https://agentmods.dev/mcp/thefraudfather/flint-plugin/agent-transaction-control"><img src="https://agentmods.dev/badge/mcp/thefraudfather/flint-plugin/agent-transaction-control.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-transaction-control 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 3d 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
{ "agent-transaction-control": { "url": "https://flint.network/mcp", "type": "streamable-http" } }
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.
- 3d ago First seen · 6 lines scan A 451454d33c52
agent-transaction-control is an MCP server published in the GitHub repository thefraudfather/flint-plugin (0 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
t2000
MCP server "t2000", hosted remotely at mcp.t2000.ai, as configured in mission69b/t2000.
402index
MCP server for 402 Index — search 15,000+ paid API endpoints across L402, x402, and MPP protocols with real-time health monitoring. Runs locally from the @402index/mcp-server npm package.
storefront-guard
Verifies a merchant storefront is legitimate before an AI agent commits payment. Runs locally from the storefront-guard-mcp-server npm package. Needs 3 environment variables to run.
evidence
Read-only verification evidence for paid machine services and buyer policy checks. Remote server at verify.atinamos.co.uk.
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.
mcp-shopee
MCP server for Shopee — LatAm marketplace Partner API v2 (orders, products, shipping, returns). Runs locally from the @codespar/mcp-shopee npm package. Needs 5 environment variables to run.