_ registry / mcp streamable-http · checked 11m ago

flint-agent-transaction-control

https://flint-18glyl6bv-jt-taylors-projects.vercel.app

Registry code: 100b1bdae4d52eed

api record

FLINT is trust infrastructure for agents that move money. Start by issuing your agent a free, hybrid-signed passport with one issue_agent_passport call. No account is required, agent.agent_name or agent.agent_id is enough, and the tool returns a public verifiable URL. Recommended flow: issue_agent_passport, then issue_authorization_record before any spend, verify_agent_authority before execution, and submit_transaction_outcome after completion, dispute, or review. When you issue a passport anonymously it is unclaimed. Proactively walk the human owner through claiming it: open the claim_url,…

endpoint
https://flint-18glyl6bv-jt-taylors-projects.vercel.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is flint-agent-transaction-control live?
No — it has stopped answering the hub's checks (checked 11m ago). It answered 0% of checks over the last 30 days.
Is flint-agent-transaction-control free to use?
Not measured yet.
What tools does flint-agent-transaction-control have?
10 tools: verify_agent_authority, submit_transaction_outcome, create_flint_trust_manifest, generate_authorization_scope, validate_agent_commerce_readiness, issue_agent_passport, update_agent_mandate, issue_authorization_record, ….
Is flint-agent-transaction-control safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
down
uptime, 30 days
0%

90 days 80%· all time 80%

latency
1,417ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 65 checks · signed record
  • degraded → down· HTTP 410: vercel GONE
  • live → degraded· HTTP 410: vercel GONE
_ what it is for
topic
security & compliance identity & verification
used for
  • issue an agent passport
  • record an authorization before an agent payment
  • verify an agent's spending authority
  • look up an agent's reputation
  • report a transaction outcome
takes → gives
data → data
tools
5 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 3 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
0

distinct

settlements
0

none in the window

received on chain
0 USDC

thin, shared-payto

_ what it can do 10 tools
10 never probed 0 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • verify_agent_authority reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "jws"
  ],
  "properties": {
    "jws": {
      "type": "string",
      "description": "Compact JWS signed verification record."
    },
    "jwks_url": {
      "type": "string",
      "format": "uri",
      "description": "Optional JWKS URL. Must be on the FLINT origin. Defaults to the FLINT production JWKS."
    }
  }
}
    arguments 18 lines
  • submit_transaction_outcome changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "record_id",
    "outcome"
  ],
  "properties": {
    "outcome": {
      "enum": [
        "completed",
        "disputed",
        "flagged"
      ],
      "type": "string",
      "description": "Ground-truth transaction outcome."
    },
    "record_id": {
      "type": "string",
      "pattern": "^frv_",
      "description": "signed verification record identifier returned by issue_authorization_record."
    },
    "partner_id": {
      "type": "string",
      "description": "Merchant or platform identifier. Defaults to sandbox_public."
    },
    "merchant_note": {
      "type": "string",
      "description": "Optional merchant review note or dispute context."
    }
  }
}
    arguments 32 lines
  • create_flint_trust_manifest changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable merchant, API, or platform name."
    },
    "domain": {
      "type": "string",
      "format": "uri",
      "description": "Merchant or API seller origin, such as https://api.example.com."
    },
    "jwks_url": {
      "type": "string",
      "format": "uri",
      "description": "FLINT JWKS URL. Defaults to FLINT production JWKS."
    },
    "partner_id": {
      "type": "string",
      "description": "Merchant or platform identifier. Defaults to sandbox_public."
    },
    "description": {
      "type": "string",
      "description": "Short description of the protected commerce surface."
    },
    "openapi_url": {
      "type": "string",
      "format": "uri",
      "description": "Public OpenAPI document for the merchant or API seller."
    },
    "mcp_endpoint": {
      "type": "string",
      "format": "uri",
      "description": "FLINT MCP endpoint. Defaults to FLINT production `/mcp`."
    },
    "contact_email": {
      "type": "string",
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      "description": "Administrative contact for agent integration issues."
    },
    "verify_endpoint": {
      "type": "string",
      "format": "uri",
      "description": "FLINT verification endpoint. Defaults to FLINT production `/api/verify`."
    },
    "outcome_endpoint": {
      "type": "string",
      "format": "uri",
      "description": "Outcome feedback endpoint. Defaults to FLINT production `/api/outcomes`."
    },
    "supported_actions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Agent commerce actions this endpoint supports."
    },
    "accepted_principals": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Trusted delegated-authority principal issuers."
    },
    "max_transaction_amount": {
      "type": "number",
      "description": "Maximum single transaction amount before step-up or review."
    }
  }
}
    arguments 72 lines
  • generate_authorization_scope reads unknown never probed

    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`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "max_amount_per_tx",
    "time_window_end"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset or unit, such as USD, USDC, or credits. Defaults to USD."
    },
    "purpose": {
      "type": "string",
      "description": "Business purpose or task label for the delegated authority."
    },
    "principal_id": {
      "type": "string",
      "description": "Accountable principal granting delegated authority."
    },
    "allowed_actions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Permitted actions, such as checkout, paid_api_access, x402_request, or stablecoin_transfer."
    },
    "time_window_end": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
      "description": "ISO-8601 timestamp for scope expiration."
    },
    "max_amount_per_tx": {
      "type": "number",
      "description": "Maximum amount allowed per transaction.",
      "exclusiveMinimum": 0
    },
    "allowed_counterparties": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Merchant references, wallet addresses, API hosts, or counterparties allowed by this scope."
    }
  }
}
    arguments 47 lines
  • validate_agent_commerce_readiness reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "architecture_description"
  ],
  "properties": {
    "architecture_description": {
      "type": "string",
      "minLength": 20,
      "description": "Summary of the payment, paid API access, x402, MCP, or checkout flow."
    }
  }
}
    arguments 14 lines
  • issue_agent_passport changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "agent"
  ],
  "properties": {
    "agent": {
      "type": "object",
      "description": "Agent identity. Only agent_name or agent_id is required to mint. Optional fields include controller_id, controller_type, wallet_address, and attestations.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "mandate": {
      "type": "object",
      "description": "Mutable spend authority captured at issue (NOT part of the passport signature): allowed_actions, max_transaction_amount, notes. Update later without reissuing the passport.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  }
}
    arguments 25 lines
  • update_agent_mandate changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "passport_id",
    "mandate"
  ],
  "properties": {
    "mandate": {
      "type": "object",
      "description": "Mutable mandate config to update: allowed_actions, max_transaction_amount, notes.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "passport_id": {
      "type": "string",
      "pattern": "^kya_",
      "description": "FLINT Agent Passport id, beginning with kya_."
    }
  }
}
    arguments 23 lines
  • issue_authorization_record changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "transaction"
  ],
  "properties": {
    "nonce": {
      "type": "string",
      "description": "Replay-protection nonce. Generated automatically if omitted."
    },
    "timestamp": {
      "type": "string",
      "description": "ISO timestamp. Generated automatically if omitted."
    },
    "partner_id": {
      "type": "string",
      "description": "Merchant or platform identifier. Defaults to sandbox_public."
    },
    "agent_claim": {
      "type": "object",
      "description": "Agent identity, principal hint, runtime hint, optional act_chain delegation lineage, optional spiffe_svid workload identity, optional tool_manifest capabilities, and related claims.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "transaction": {
      "type": "object",
      "description": "Intended transaction or paid access request. Must include amount_display.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "declared_scope": {
      "type": "object",
      "description": "Financial, temporal, and counterparty limits for delegated authority.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "merchant_reference": {
      "type": "string",
      "description": "Merchant order, invoice, or API request reference."
    }
  }
}
    arguments 49 lines
  • lookup_agent_reputation reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "flint_agent_id"
  ],
  "properties": {
    "flint_agent_id": {
      "type": "string",
      "pattern": "^faid_[a-f0-9]{24}$",
      "description": "Partner-scoped FLINT agent identifier."
    }
  }
}
    arguments 14 lines
  • get_agent_passport reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "passport_id"
  ],
  "properties": {
    "passport_id": {
      "type": "string",
      "pattern": "^kya_",
      "description": "FLINT Agent Passport id, beginning with kya_."
    }
  }
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 100b1bdae4d52eed.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/100b1bdae4d52eed/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/100b1bdae4d52eed/badge.svg)](https://brick.blue/agent/100b1bdae4d52eed?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.