Categories › Business & Finance › Payments & billing
What the chain records about an address before you pay it, and whether a payment fits it.
Remote server: your requests and data go to aspern.org. Claude Code: claude mcp add --transport http aspern-counterparty-checks-for-agents https://aspern.org/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
identify — Call this FIRST whenever you hold something other than a wallet address. Give it a transaction hash, an http(s) URL, a hostname or an ERC-80check_service_endpoint — Call this before connecting to a service. Give it the http(s) URL of an MCP or A2A endpoint and it says who declares it, whether our daily ppreflight_payment — Call this immediately before sending a payment, every time — not once per counterparty. It weighs THIS payment (the amount, the chain, the evault_assessment — THE HASH-COMMITTED ASSESSMENT OF A VAULT, in the shape ERC-8004’s Reputation Registry points at, and the only thing here a third party can pvault_exits — SEND `exitAmountUsd` WITH THE POSITION YOU ARE WEIGHING and this answers whether that size has ever cleared here: the schema has carried it vault_risk_dimensions — SIX RISKS, NOT ONE WORD, across every vault we score. A risk band is a weighted whole and a reader takes it as a summary of everything, whicportfolio_screen — READ THE VAULTS YOU HOLD TOGETHER. This one is about a SET rather than a single subject; an allocator does not hold one subject. This answercapital_coverage — BEFORE YOU TRUST ANY COVERAGE FIGURE FROM US, ask this. It says how much of the market each vault reading actually covers, counted TWO WAYS:exit_lifecycle_coverage — HOW MUCH OF THE WAY OUT WE CAN SEE, phase by phase, across every open vault. Getting out has four phases — a request filed, something set asendpoint_coverage — BEFORE YOU TREAT ANY ENDPOINT AS RELIABLE, ask how well we know. There is no uptime number here and there will not be one, because the statepayment_evidence — BEFORE YOU QUOTE ANY FIGURE FOR AGENT COMMERCE, ask which of three it is. Every payment shown to be one, x402 and ACP, is split into three fevidence_for — Everything we hold about one subject, as edges, each carrying where it came from. Use it when you need to explain a decision rather than jusevaluate_action — Call this when you are about to DO something and need one answer you can act on: pay an address, connect to an MCP server, call a tool, or pevaluate_vault_decision — Call this before an agent moves capital into or out of a vault, with the decision it is about to make: the vault, the amount, the MANDATE itsimulate_withdrawal — TRY ONE WITHDRAWAL FROM A VAULT BEFORE YOU MAKE IT. Runs the vault’s own withdraw(amount, holder, holder) by eth_call at the head block, as test_purchase — WALK THE WHOLE PURCHASE OF AN x402 ENDPOINT WITHOUT PAYING, in the order a buyer actually asks the questions, stopping at the first one thatknock_on_endpoint — KNOCK ON AN x402 ENDPOINT AND GET WHAT IT SERVED. `test_purchase` beside this walks a buy WITHOUT paying and stops at the quote; its own cavendpoint_disagreements — WHICH ENDPOINTS CONTRADICT THEIR OWN LISTING: they ask to be paid at an address the catalogue entry they published does not name. The contralist_x402_endpoints — WHICH ENDPOINTS A PAYEE SELLS, or which ones match some text. The sharpest check a payment can get is the endpoint being bought, and until tlist_policies — The policies evaluate_action can be run under, in full: every rule, its id and the sentence it checks. Published deliberately, including to counterparty_check — Before paying or hiring an agent: what the chain records about that address. `byNetwork` splits it network by network: x402 payments receivevault_sanctions_screening — One vault against the OFAC SDN list: its contract roles and its direct holders where the holder list is complete, exact address matches onlyvault_due_diligence — The due-diligence report on one vault, cut to what an agent acts on: overallAssessment (published, conditional or withheld; publishedBand isvault_drift — What changed on one vault, day by day, between the stored daily due-diligence reports: the overall assessment (including when it became withcounterparty_evidence — Before trading with an agent or service: what the records actually say about it, in one answer. Identity links with their strength (declaredvault_check — Before putting capital into a vault: what the record shows about it. The headline is what a holder ACTUALLY EARNED set against the advertisefind_vaults — Find a vault by what it has DONE rather than what it is called. Free. The filter worth knowing is `earned`: `short` returns the vaults whereoperator_check — The question that follows vault_check: who runs the money, and how much of it is their own. Free. Read `ownShare` with its limits, which tralist_vaults — The vaults we read, so a caller holding a name rather than a slug can find the one it means. Free. Absence from this list means we do not refind_agents — Find PAID ON-CHAIN SERVICES (an x402 seller, an ACP or Olas worker, a Masumi agent) by what the chain records rather than what they claim. Mcounterparty_history — How one agent’s record has moved: dealings, independent payers, concentration and delivery, day by day. PAID, one cent a call over x402 — thvaults_earned — What depositors actually KEPT, against what their vault advertised. READ `population` BEFORE QUOTING ANY SHARE FROM THIS. The comparison covagent_changes — What moved in the agent record, across every agent, since a date. The counterparty check answers what is true about one address NOW; this ancounterparty_bulk — Check up to fifty addresses in one call, each with its observations, AND what the set shares underneath: the parties that two or more of theagent_dependencies — If your firm relies on several external agents, what do they rest on AT ONCE? Give it two to twenty-five addresses and it finds the parties agent_business — Does this agent have a BUSINESS, and can any of it be demonstrated? Six questions an investor, a marketplace or an operator actually asks, eagent_economic_profile — One agent, four readings, in the order a buyer actually asks them: what it EARNS and from whom, whether its contracted work FINISHED and whoexit_screen — YOU HAVE A SIZE AND YOU WANT TO KNOW WHERE IT HAS ACTUALLY CLEARED. Every other exit reading here is about one vault; this asks the same quevault_exit_confidence — Before you put capital in, ask what evidence there is that you could get a PARTICULAR amount back out. Every other reading about a vault is check_action — CALL THIS BEFORE YOUR AGENT SIGNS ANYTHING THAT MOVES MONEY. One request instead of five: it reads the counterparty record, decodes the callNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.