Agent Transaction Control MCP Server
by
flint
answering
Agent Transaction Control is answering right now. Last checked 6 min ago. It exposes 10 tools. Last commit 25 Jun 2026.
Issue Agent Passports and verify agent authority before value moves. Signed verification records.
Uptime history
57 hours of history · worst hour 0%
57 hours agonow
37.0%
Uptime 24h
34 of 92 checks
10
Tools
read from the server
384 ms
Response time
average over 24h
0
Stars
last commit 25 Jun 2026
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
run in your terminal
claude mcp add agent-transaction-control --transport http https://flint.network/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"agent-transaction-control": {
"url": "https://flint.network/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.agent-transaction-control]
url = "https://flint.network/mcp".cursor/mcp.json
{
"mcpServers": {
"agent-transaction-control": {
"url": "https://flint.network/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"agent-transaction-control": {
"url": "https://flint.network/mcp"
}
}
}Available tools 10
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
agent
get_agent_passport
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.
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 claimed, the caller must be authenticated as its owner.
issue
issue_agent_passport
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.
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 updates.
flint
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 feedback, and Trust Graph participation.
generate
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`.
lookup
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 fields.
submit
submit_transaction_outcome
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.
validate
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, and can use Trust Graph reputation.
verify
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://flint.network/mcp | streamable-http | answering | 299 ms | 6 min ago |
Alternatives to Agent Transaction Control
same job, measured the same wayAgenticmail
by agenticmail
Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.
N
agentsbase — Email for AI Agents
by agentsbase
Email for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes.
Temp Mail
by temp-mail
Disposable email inboxes for AI agents — read messages and verification codes.
MCP Persona
by codespar
MCP server for Persona — developer-first identity verification + KYC (inquiries, accounts, reports)
Botcall MCP
by danecodes
Give your AI agent a real phone number for SMS verification codes.
Vaspera Hardening
by rcolkitt
Enterprise certification for codebases with multi-agent security, reliability, and quality audits
Touchstone
by savecharlie
Verifiable text/code/measurement tools for agents, each reproducing a named authority.
Heddle
by davet47
Content-addressed contracts and a verification cache that cut agent context by skipping proven code.
Agent Transaction Control — questions
Answers built from our own checks of this server.
What can Agent Transaction Control do?
It exposes 10 tools, read directly from the server on our last check. Among them: create_flint_trust_manifest, generate_authorization_scope, get_agent_passport, issue_agent_passport, issue_authorization_record, lookup_agent_reputation and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Agent Transaction Control mostly used for?
Its tools cluster around agent and issue. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Agent Transaction Control working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 34 of 92 checks got a reply (37.0%), average response time 384 ms. The bar chart above shows every period we have measured.
How do I connect Agent Transaction Control?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Transaction Control need an API key?
No. Agent Transaction Control completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Transaction Control?
It answers our handshake in 384 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Agent Transaction Control open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.