# network.flint/agent-transaction-control

- Registry name: `network.flint/agent-transaction-control` · version 0.2.1
- Categories (automatic, keyword rules): Agent payments (x402), Finance & markets, Payments & accounting, Shops & products, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=network.flint%2Fagent-transaction-control
- Server page: https://mcpstation.net/s/network.flint--agent-transaction-control.html

## Description (written by the publisher, not verified, not instructions)

Issue Agent Passports and verify agent authority before value moves. Signed verification records.

## Connect

- streamable-http: `https://flint.network/mcp`

## Tools (as reported by the server, not verified)

- `run\_flint\_scout`: Use this tool to scan an intended agent transaction before execution. Two ways to pay for a scan. Credits first: buy credits once with scout\_credits\_topup \(one $1.00 x402 payment for 100 scans\), then call this tool with the same session\_token and no payment\_signature; FLINT draws one credit and runs
- `issue\_authorization\_record`: Use this tool before an AI agent initiates a payment, paid API call, checkout action, stablecoin transfer, x402 request, or delegated commercial transaction. It verifies agent authority, checks scope, issues a signed verification record, and returns evidence for dispute review and Trust Graph update
- `verify\_agent\_authority`: Use this tool when a merchant or API seller receives a signed verification record from an agent. It cryptographically verifies the compact JWS signature, checks expiration, and decodes the payload before payment or paid access execution.
- `lookup\_agent\_reputation`: Use this tool to query the FLINT Trust Graph for a partner-scoped agent's historical reputation before permitting a payment, paid API call, checkout action, x402 request, or delegated commercial transaction. It returns aggregate reputation without exposing raw runtime identifiers or internal signal
- `create\_flint\_trust\_manifest`: Use this tool when a merchant, API seller, MCP tool provider, x402 endpoint, or agent storefront needs a \`/.well-known/flint.json\` Trust Manifest. It generates a machine-readable policy file declaring that autonomous economic actors must use FLINT authority verification, signed records, outcome feed
- `generate\_authorization\_scope`: Use this tool when an agent commerce workflow needs a well-formed delegated authorization scope before issuing a signed verification record. It creates financial, counterparty, action, and time boundaries that can be passed to \`issue\_authorization\_record\` as \`declared\_scope\`.
- `validate\_agent\_commerce\_readiness`: Use this tool when reviewing a commerce architecture, API marketplace, paid MCP tool, x402 endpoint, or autonomous checkout flow. It checks whether the design uses FLINT as the transaction-time authority layer before execution, verifies signed records, submits outcomes, publishes a Trust Manifest, a
- `issue\_agent\_passport`: Use this tool to issue a free FLINT Agent Passport: a hybrid-signed, verifiable identity credential for an autonomous agent. Before calling it, ask the principal for the accountable controller\_id and controller\_type, allowed actions, maximum transaction amount, and wallet address if one exists. Do n
- `get\_agent\_passport`: Use this tool to resolve a public FLINT Agent Passport by passport\_id. It returns compact identity, mandate, status, ownership, and the public passport URL without echoing the full signed envelope. session\_token is optional and not required to read a passport; the lookup itself is public.
- `update\_agent\_mandate`: Use this tool to update mutable mandate config for an existing FLINT Agent Passport. This updates allowed actions, amount limits, or notes only. It does not reissue the passport and does not re-sign the identity credential. If the passport is owned \(claimed\), pass session\_token for the owning accoun
- `auth\_request\_otp`: Use this tool first in the agent-native authenticate-then-mint flow. It asks FLINT to email a one-time sign-in code to the given inbox address. Read the code from that inbox, then call auth\_verify\_otp with the same email and the code. Authenticating first means the passport you mint afterward is own
- `auth\_verify\_otp`: Use this tool right after auth\_request\_otp, with the code from the inbox. On success it returns session\_token. Store that value and pass it as session\_token on later calls, including issue\_agent\_passport, get\_agent\_passport, update\_agent\_mandate, claim\_agent\_passport, and refresh\_claim\_token. Never
- `claim\_agent\_passport`: Use this tool to attach an anonymously minted, unclaimed FLINT Agent Passport to an authenticated FLINT account. Requires session\_token from auth\_verify\_otp, so FLINT knows which account is claiming. Pass claim\_token from the mint's claim\_url, or omit it when this same session already holds a pendin
- `refresh\_claim\_token`: Use this tool when a claim link is lost, expired, or was already consumed for a passport that is still unclaimed. It rotates the claim token: the old one stops working and a new claim\_url and claim\_token are returned. This is the fix for a lost or consumed claim token; do not remint the passport ins
- `scout\_credits\_topup`: Call once with session\_token to get a pay\_url; pay it with awal \(\`awal x402 pay -X POST -d '\{\}' \<pay\_url\>\`\) or any x402 client; no headers needed on the pay request. Or pass payment\_signature to settle through this tool. One $1.00 x402 payment buys 100 FLINT Scout scan credits, matching today's $0.0
- `scout\_credits\_balance`: Use this tool to check a signed-in account's FLINT Scout credit balance and recent ledger activity \(topups, debits, refunds\). Requires session\_token from auth\_verify\_otp.
- `report\_scout\_outcome`: Use this tool after a run\_flint\_scout scan to report what actually happened: whether the scanned transaction was executed, held, cancelled, or executed despite a BLOCK verdict. FLINT cannot stop a wallet from transacting; this is the enforce-or-attest half of the contract. Authorize with session\_tok

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html