accueil / serveurs / IA & Mémoire / network.flint/agent-transaction-control
network.flint/agent-transaction-control
serveur MCP (Model Context Protocol) · flint-agent-transaction-control 0.5.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que network.flint/agent-transaction-control est sûr ?
Au dernier audit MCP Hub, le serveur MCP « network.flint/agent-transaction-control » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 17 outils
- auth_request_otp≈ 236 tokens
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 owned by the account immediately, with no separate claim step.
Paramètres, retour & exemple (1)
Paramètresemail· string · requis
Inbox address that will receive the one-time sign-in code.
Exemple d'appel{"name": "auth_request_otp", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - auth_verify_otp≈ 306 tokens
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 print or log session_token; treat it like a password.
Paramètres, retour & exemple (3)
Paramètrescode· string · requis
The one-time sign-in code from the inbox.email· string · requis
The same inbox address auth_request_otp was called with.label· string · optionnel
Optional human-readable label for this session, such as the agent or workflow name.
Exemple d'appel{"name": "auth_verify_otp", "arguments": {"code": "texte", "email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - claim_agent_passport≈ 352 tokens
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 pending claim for this passport_id. Once claimed the passport is owned and Sentinel protection turns on. A passport can only be claimed once; if the token was already used or lost, call refresh_claim_token for a fresh one instead of trying to remint.
Paramètres, retour & exemple (3)
Paramètresclaim_token· string · optionnel
The one-time claim token from claim_url. Omit only when this session already started a pending claim for this passport.passport_id· string · requis
FLINT Agent Passport id, beginning with kya_.session_token· string · requis
Agent session token from auth_verify_otp for the account that is claiming this passport.
Exemple d'appel{"name": "claim_agent_passport", "arguments": {"passport_id": "texte", "session_token": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - create_flint_trust_manifest≈ 588 tokens
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 feedback, and Trust Graph participation.
Paramètres, retour & exemple (13)
Paramètresname· string · optionnel
Human-readable merchant, API, or platform name.domain· string · optionnel
Merchant or API seller origin, such as https://api.example.com.jwks_url· string · optionnel
FLINT JWKS URL. Defaults to FLINT production JWKS.partner_id· string · optionnel
Merchant or platform identifier. Defaults to sandbox_public.description· string · optionnel
Short description of the protected commerce surface.openapi_url· string · optionnel
Public OpenAPI document for the merchant or API seller.mcp_endpoint· string · optionnel
FLINT MCP endpoint. Defaults to FLINT production `/mcp`.contact_email· string · optionnel
Administrative contact for agent integration issues.verify_endpoint· string · optionnel
FLINT verification endpoint. Defaults to FLINT production `/api/verify`.outcome_endpoint· string · optionnel
Outcome feedback endpoint. Defaults to FLINT production `/api/outcomes`.supported_actions· array · optionnel
Agent commerce actions this endpoint supports.accepted_principals· array · optionnel
Trusted delegated-authority principal issuers.max_transaction_amount· number · optionnel
Maximum single transaction amount before step-up or review.
Exemple d'appel{"name": "create_flint_trust_manifest", "arguments": {"name": "texte", "domain": "texte", "jwks_url": "texte", "partner_id": "texte", "description": "texte", "openapi_url": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - generate_authorization_scope≈ 454 tokens
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`.
Paramètres, retour & exemple (7)
Paramètresasset· string · optionnel
Asset or unit, such as USD, USDC, or credits. Defaults to USD.purpose· string · optionnel
Business purpose or task label for the delegated authority.principal_id· string · optionnel
Accountable principal granting delegated authority.allowed_actions· array · optionnel
Permitted actions, such as checkout, paid_api_access, x402_request, or stablecoin_transfer.time_window_end· string · requis
ISO-8601 timestamp for scope expiration.max_amount_per_tx· number · requis
Maximum amount allowed per transaction.allowed_counterparties· array · optionnel
Merchant references, wallet addresses, API hosts, or counterparties allowed by this scope.
Exemple d'appel{"name": "generate_authorization_scope", "arguments": {"time_window_end": "texte", "max_amount_per_tx": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_agent_passport≈ 209 tokens
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.
Paramètres, retour & exemple (2)
Paramètrespassport_id· string · requis
FLINT Agent Passport id, beginning with kya_.session_token· string · optionnel
Optional agent session token from auth_verify_otp.
Exemple d'appel{"name": "get_agent_passport", "arguments": {"passport_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - issue_agent_passport≈ 1158 tokens
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 not infer or invent authority. For the strongest available setup, authenticate first and mint with the principal-supplied identity and mandate. The zero-config path only needs agent.agent_name or agent.agent_id, but that result is identity-only and is not ready to transact until the missing authority is supplied. A missing controller requires a corrected remint because signed identity is immutable; a missing mandate can be added later. The passport signs identity only; the spending mandate is separate, mutable config that can be updated later without reissuing the passport. Pass session_token, from auth_verify_otp, to mint owned: the passport binds to your authenticated account immediately and there is no claim step or claim_url. Omit session_token to mint anonymously instead; that returns a one-time claim_url and the passport stays unclaimed until someone signs in and claims it. controller_id identifies who is accountable on the signed identity, which is not the same as the FLINT account that owns the passport; controller_name is a separate, optional, human-readable display label. Allowed actions must come from the FLINT mandate vocabulary: commerce_purchase, checkout.purchase, invoice.pay, subscription.renew, refund.request, quote.retrieve, x402_verification_purchase, stablecoin_transfer, paid_api_access, x402_request, agent_checkout, delegated_spending, project.read. Pass ["ALL"] as a preset to grant every action in one step; the stored mandate then expands to the full list and records the preset. Unknown strings are kept for backward compatibility but are reported back as unknown so the caller can fix them. The signed identity is immutable once minted, so a wrong agent_id, controller_id, or controller_type cannot be edited in place. Fix it by reminting with the corrected fields. A remint that reuses the same agent_id and controller_id supersedes a prior UNCLAIMED passport for that pair ONLY when this mint is authorized: either session_token proves the same controller (controller_assurance verified or command), or supersede_management_token matches that specific prior passport's own management token (the raw claim token from its claim_url). Without either, the prior is left alone, still indexed, and reported back as related_passports with a warning, so a stranger cannot anonymously remint someone else's controller_id and agent_id to burn their pending claim. A prior CLAIMED passport is never superseded automatically; it is listed back as existing_claimed_passports with a warning so you can review it by hand. Returns a public, resolvable passport URL and, when minted anonymously, a one-time claim link.
Paramètres, retour & exemple (4)
Paramètresagent· object · requis
Agent identity. Only agent_name or agent_id is required for an identity-only mint. Ask the principal for controller_id and controller_type before minting a Passport intended for transactions. Optional fields include controller_name, wallet_address, and attestations. Never invent principal authority.mandate· object · optionnel
Principal-supplied mutable authority captured at issue (NOT part of the passport signature): allowed_actions, max_transaction_amount, notes. Ask the principal for these values and never infer them. Update later without reissuing the passport.session_token· string · optionnel
Optional agent session token from auth_verify_otp. When present the passport is owned by that account at issuance and no claim step is needed.supersede_management_token· string · optionnel
Optional. The management_token (raw claim token) of a specific prior UNCLAIMED passport with the same agent_id and controller_id. Presenting it authorizes superseding that prior passport even with no session_token, since it proves possession of that prior's own claim link.
Exemple d'appel{"name": "issue_agent_passport", "arguments": {"agent": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - issue_authorization_record≈ 442 tokens
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 updates.
Paramètres, retour & exemple (7)
Paramètresnonce· string · optionnel
Replay-protection nonce. Generated automatically if omitted.timestamp· string · optionnel
ISO timestamp. Generated automatically if omitted.partner_id· string · optionnel
Merchant or platform identifier. Defaults to sandbox_public.agent_claim· object · optionnel
Agent identity, principal hint, runtime hint, optional act_chain delegation lineage, optional spiffe_svid workload identity, optional tool_manifest capabilities, and related claims.transaction· object · requis
Intended transaction or paid access request. Must include amount_display.declared_scope· object · optionnel
Financial, temporal, and counterparty limits for delegated authority.merchant_reference· string · optionnel
Merchant order, invoice, or API request reference.
Exemple d'appel{"name": "issue_authorization_record", "arguments": {"transaction": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - lookup_agent_reputation≈ 181 tokens
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 fields.
Paramètres, retour & exemple (1)
Paramètresflint_agent_id· string · requis
Partner-scoped FLINT agent identifier.
Exemple d'appel{"name": "lookup_agent_reputation", "arguments": {"flint_agent_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - refresh_claim_token≈ 346 tokens
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 instead, reminting only supersedes prior unclaimed passports and does not recover a lost claim link. Authorize with the current management_token (the raw claim token, even one about to be superseded), or with session_token when this session originally requested the claim or minted the passport.
Paramètres, retour & exemple (3)
Paramètrespassport_id· string · requis
FLINT Agent Passport id, beginning with kya_.session_token· string · optionnel
Optional agent session token from auth_verify_otp, used when management_token is unavailable.management_token· string · optionnel
The current claim or management token for this passport.
Exemple d'appel{"name": "refresh_claim_token", "arguments": {"passport_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - report_scout_outcome≈ 513 tokens
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_token when the caller's account owns the presented passport, or with caller_binding_token from the scan's caller_obligation block when acting anonymously. Executing after BLOCK is recorded on the record as an override and alerts the passport owner.
Paramètres, retour & exemple (7)
Paramètresnote· string · optionnel
Optional free-text note, at most 280 characters.chain· string · optionnel
CAIP-2 chain identifier for tx_hash, such as eip155:8453.outcome· string · requis · executed | held | executed_despite_block | cancelled
What actually happened to the scanned transaction.tx_hash· string · optionnel
On-chain transaction hash. Optional, but expected when outcome starts with executed.record_id· string · requis
The signed record id returned by run_flint_scout, beginning with frv_.session_token· string · optionnel
Agent session token from auth_verify_otp, when the caller's account owns the presented passport.caller_binding_token· string · optionnel
The caller_binding_token from the scan's caller_obligation block, for an anonymous caller reporting its own outcome without an account.
Exemple d'appel{"name": "report_scout_outcome", "arguments": {"outcome": "executed", "record_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - run_flint_scout≈ 1201 tokens
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 the scan immediately, with no wallet signature for that call. x402 per call second: with no session_token, the first call returns a $0.01 x402 payment challenge without running the scan; a wallet-enabled client signs that challenge and retries with payment_signature. Either way, when the call returns a 402 instead of a result, the result carries pay_recipe with concrete next steps: an awal command, a local script, the credits path, and the browser flow. After a paid or credit-funded scan completes, FLINT returns a signed authority decision. When receipt issuance succeeds for a paid scan, it also returns a separately signed settlement receipt and durable receipt URL; otherwise it reports receipt unavailability without inviting a paid retry. Payment to FLINT is distinct from the transaction being scanned and is not proof of agent authority.
Paramètres, retour & exemple (8)
Paramètresnonce· string · optionnel
Replay-protection nonce. Generated automatically if omitted.timestamp· string · optionnel
ISO-8601 request timestamp. Generated automatically if omitted.agent_claim· object · optionnel
Optional bounded agent hints. Self-asserted values do not establish authority.passport_id· string · optionnel
Optional FLINT Agent Passport. Verified payer-wallet and mandate bindings may strengthen the decision.transaction· object · requissession_token· string · optionnel
Optional agent session token from auth_verify_otp. When present with no payment_signature, FLINT draws one prepaid Scout credit instead of requiring an x402 payment for this call. Buy credits first with scout_credits_topup.payment_signature· string · optionnel
Opaque caller-signed x402 PAYMENT-SIGNATURE value from a wallet-enabled client. Never provide a private key or seed phrase.merchant_reference· string · optionnel
Optional merchant reference. Must match transaction.reference when both are supplied.
Exemple d'appel{"name": "run_flint_scout", "arguments": {"transaction": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - scout_credits_balance≈ 157 tokens
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.
Paramètres, retour & exemple (1)
Paramètressession_token· string · requis
Agent session token from auth_verify_otp for the account to check.
Exemple d'appel{"name": "scout_credits_balance", "arguments": {"session_token": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - scout_credits_topup≈ 475 tokens
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.01 x402 price without signing a payment for every run_flint_scout call. Requires session_token from auth_verify_otp so the credits land on that account; call auth_request_otp then auth_verify_otp first if you do not have one. With no topup_id, the first call creates a fresh top-up intent (an sct_ id good for 24 hours) and returns its pay_url alongside the same $1.00 x402 challenge. Pass topup_id to retry paying or settling that same intent instead of creating a new one. Once credited, call run_flint_scout with the same session_token and no payment_signature to draw one credit per scan.
Paramètres, retour & exemple (3)
Paramètrestopup_id· string · optionnel
Optional existing top-up intent id from a prior call, to retry paying or settling it instead of creating a new one. Intents expire 24 hours after creation.session_token· string · requis
Agent session token from auth_verify_otp. Credits are added to this account.payment_signature· string · optionnel
Opaque caller-signed x402 PAYMENT-SIGNATURE value from a wallet-enabled client. Never provide a private key or seed phrase.
Exemple d'appel{"name": "scout_credits_topup", "arguments": {"session_token": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - update_agent_mandate≈ 474 tokens
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 account; management_token is only needed while the passport is unclaimed. Allowed actions must come from the FLINT mandate vocabulary: commerce_purchase, checkout.purchase, invoice.pay, subscription.renew, refund.request, quote.retrieve, x402_verification_purchase, stablecoin_transfer, paid_api_access, x402_request, agent_checkout, delegated_spending, project.read. Pass ["ALL"] as a preset to grant every action in one step; the stored mandate then expands to the full list and records the preset. Unknown strings are kept for backward compatibility but are reported back as unknown so the caller can fix them.
Paramètres, retour & exemple (4)
Paramètresmandate· object · requis
Mutable mandate config to update: allowed_actions, max_transaction_amount, notes.passport_id· string · requis
FLINT Agent Passport id, beginning with kya_.session_token· string · optionnel
Optional agent session token from auth_verify_otp, used once the passport is owned.management_token· string · optionnel
Claim token required while the Passport is unclaimed.
Exemple d'appel{"name": "update_agent_mandate", "arguments": {"mandate": {}, "passport_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - validate_agent_commerce_readiness≈ 202 tokens
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, and can use Trust Graph reputation.
Paramètres, retour & exemple (1)
Paramètresarchitecture_description· string · requis
Summary of the payment, paid API access, x402, MCP, or checkout flow.
Exemple d'appel{"name": "validate_agent_commerce_readiness", "arguments": {"architecture_description": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify_agent_authority≈ 285 tokens
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.
Paramètres, retour & exemple (4)
Paramètresjws· string · requis
Compact JWS signed verification record.jwks_url· string · optionnel
Optional JWKS URL. Must be on the FLINT origin. Defaults to the FLINT production JWKS.expected_partner_id· string · requis
Partner identifier expected in the authorization record.expected_merchant_reference· string · requis
Current transaction or resource reference expected in the authorization record.
Exemple d'appel{"name": "verify_agent_authority", "arguments": {"jws": "texte", "expected_partner_id": "texte", "expected_merchant_reference": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».