ZBS Index What actually exists in applied AI, with the source next to it

mcp server

agent-transaction-control

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

Description as published by the maintainer. Source

  • version 0.2.1
  • active

active — Registry entry last updated 2026-06-23.

What this server can do

10 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

create_flint_trust_manifest(name, domain, jwks_url, partner_id, description, openapi_url, mcp_endpoint, contact_email, verify_endpoint, outcome_endpoint, supported_actions, accepted_principals, max_transaction_amount)
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.
generate_authorization_scope(asset, purpose, principal_id, allowed_actions, time_window_end, max_amount_per_tx, allowed_counterparties)
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`. Required: max_amount_per_tx, time_window_end.
get_agent_passport(passport_id)
Use this tool to resolve a public FLINT Agent Passport by passport_id. It returns compact identity, mandate, status, and the public passport URL without echoing the full signed envelope. Required: passport_id.
issue_agent_passport(agent, mandate)
Use this tool to issue a free FLINT Agent Passport: a hybrid-signed, verifiable identity credential for an autonomous agent. The zero-config mint path only needs agent.agent_name or agent.agent_id. Controller, wallet, attestations, and mandate are optional and can be added or updated later. The passport signs identity only; the spending mandate is separate, mutable config that can be updated later without reissuing the passport. Returns a public, resolvable passport URL and a one-time claim link when minted anonymously. Required: agent.
issue_authorization_record(nonce, timestamp, partner_id, agent_claim, transaction, declared_scope, merchant_reference)
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. Required: transaction.
lookup_agent_reputation(flint_agent_id)
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. Required: flint_agent_id.
submit_transaction_outcome(outcome, record_id, partner_id, merchant_note)
Use this tool after a FLINT-authorized transaction, paid API call, checkout action, x402 request, or delegated commercial action completes, is disputed, or is flagged. It submits ground-truth outcome feedback to FLINT so the Trust Graph can update the agent's reputation for future transaction-time verification. Required: record_id, outcome.
update_agent_mandate(mandate, passport_id)
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 claimed, the caller must be authenticated as its owner. Required: passport_id, mandate.
validate_agent_commerce_readiness(architecture_description)
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. Required: architecture_description.
verify_agent_authority(jws, jwks_url)
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. Required: jws.

Last successful function declaration observed on . Source: https://flint.network/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://flint.network/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 0.2.1 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-06-23 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-06-23 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 10 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe flint.network
mcp endpoint status ok The server listed 10 functions when asked. as of probe flint.network

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://flint.network/mcp — flint.network, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.