Home / MCP registry index / network.flint/agent-transaction-control
network.flint/agent-transaction-control
network.flint/agent-transaction-control in the official MCP registry.
Endpoint https://flint.network/mcp. Source: github.com/thefraudfather/flint-plugin.
The registry describes it as: Issue Agent Passports and verify agent authority before value moves. Signed verification records.
We read its 17 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
run_flint_scout issue_authorization_record verify_agent_authority lookup_agent_reputation create_flint_trust_manifest generate_authorization_scope validate_agent_commerce_readiness issue_agent_passport get_agent_passport update_agent_mandate auth_request_otp auth_verify_otp claim_agent_passport refresh_claim_token scout_credits_topup scout_credits_balance report_scout_outcome
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/network-flint-agent-transaction-control)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.