ASPERN: counterparty checks for agents
OnlineWhat the chain records about an address before you pay it, and whether a payment fits it.
What it can do: 60 tools
identifyread-onlyCall 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-8004 registration number and it says which party that is, with the evidence for thcheck_service_endpointread-onlyCall 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 probe reached it, what it answered with, and how many of the last readings answerpreflight_paymentread-onlyCall this immediately before sending a payment, every time — not once per counterparty. It weighs THIS payment (the amount, the chain, the endpoint) against what the address has actually done: the price the seller themsevault_assessmentread-onlyTHE 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 publish on chain under their own name. Until 2026-10-21 this document was reachabvault_exitsread-onlySEND `exitAmountUsd` WITH THE POSITION YOU ARE WEIGHING and this answers whether that size has ever cleared here: the schema has carried it since 2026-10-08, and an auditor still had to find it by guessing because this svault_risk_dimensionsSIX 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, which it is not: ours weighs drawdown, crowding, exit, concentration and consistencyportfolio_screenread-onlyREAD THE VAULTS YOU HOLD TOGETHER. This one is about a SET rather than a single subject; an allocator does not hold one subject. This answers the three questions that only exist across holdings and that no vault page cancapital_coverageread-onlyBEFORE YOU TRUST ANY COVERAGE FIGURE FROM US, ask this. It says how much of the market each vault reading actually covers, counted TWO WAYS: by number of open vaults and by the capital in them. They differ by a lot, andexit_lifecycle_coverageread-onlyHOW 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 aside to claim, money that actually left, and an attempt that failed — and we readendpoint_coverageread-onlyBEFORE 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 states mean different things and summing them produces a figure about nothing: a 402payment_evidenceread-onlyBEFORE 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 figures that NEST and are never added up (x402 counts only the `protocol`, `routeevidence_forread-onlyEverything we hold about one subject, as edges, each carrying where it came from. Use it when you need to explain a decision rather than just make one, or to see what is MISSING before you act. Every edge has `source`, `evaluate_actionread-onlyCall 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 put capital into a vault. The answer depends on the AMOUNT, the ACTION, the POLICevaluate_vault_decisionCall 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 it must stay inside and the CLAIMS the decision rests on. It is judged against oursimulate_withdrawalTRY 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 the holder you name or, if you name none, as its largest depositor: the contracttest_purchaseWALK THE WHOLE PURCHASE OF AN x402 ENDPOINT WITHOUT PAYING, in the order a buyer actually asks the questions, stopping at the first one that objects. All five are asked in one pass and in that order, so the walk stops whknock_on_endpointKNOCK 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 caveat has always said that only paying and reading the answer establishes what arrendpoint_disagreementsread-onlyWHICH ENDPOINTS CONTRADICT THEIR OWN LISTING: they ask to be paid at an address the catalogue entry they published does not name. The contradiction appears only when the live handshake and the published listing are heldlist_x402_endpointsread-onlyWHICH ENDPOINTS A PAYEE SELLS, or which ones match some text. The sharpest check a payment can get is the endpoint being bought, and until this a caller had to know its URL by heart. Nearly every catalogued resource namelist_policiesread-onlyThe policies evaluate_action can be run under, in full: every rule, its id and the sentence it checks. Published deliberately, including to the agents being evaluated — a rule nobody can read is a rule nobody can correctcounterparty_checkread-onlyBefore paying or hiring an agent: what the chain records about that address. `byNetwork` splits it network by network: x402 payments received (and their dollars, stablecoins at face value), ACP jobs and paid dollars, Olavault_sanctions_screeningOne vault against the OFAC SDN list: its contract roles and its direct holders where the holder list is complete, exact address matches only, with the list version and whether it is current. Paid ($0.01). States: EXACT_Lvault_due_diligenceThe due-diligence report on one vault, cut to what an agent acts on: overallAssessment (published, conditional or withheld; publishedBand is null when withheld and partialBand is never the verdict), findings above the bavault_driftWhat changed on one vault, day by day, between the stored daily due-diligence reports: the overall assessment (including when it became withheld or published again), each risk dimension, the withdrawable share, capital,counterparty_evidenceBefore trading with an agent or service: what the records actually say about it, in one answer. Identity links with their strength (declared by the agent, observed by us, or corroborated by a second party), settled paymevault_checkread-onlyBefore putting capital into a vault: what the record shows about it. The headline is what a holder ACTUALLY EARNED set against the advertised rate, with the risk band, the components that apply, who runs it, and `keys`:find_vaultsread-onlyFind a vault by what it has DONE rather than what it is called. Free. The filter worth knowing is `earned`: `short` returns the vaults where a holder earned LESS than the venue advertises — how many there are is in the aoperator_checkread-onlyThe question that follows vault_check: who runs the money, and how much of it is their own. Free. Read `ownShare` with its limits, which travel inside it: the leader’s holding is readable on Hyperliquid and Drift ONLY, slist_vaultsread-onlyThe 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 read that vault, never that it does not exist.find_agentsread-onlyFind 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. MOST ARE NOT SHOWN TO BE AI AGENTS: every row is a paid on-chain service, and `sucounterparty_historyHow one agent’s record has moved: dealings, independent payers, concentration and delivery, day by day. PAID, one cent a call over x402 — the median price of this rail. Without payment the tool answers with the price andstock_pegDoes each token of one share hold that share’s price? Per token: the share on its exchange times the shares the token stands for, against the issuer’s reference and the deepest DEX pool, with the gap now and over the lasvaults_earnedread-onlyWhat depositors actually KEPT, against what their vault advertised. READ `population` BEFORE QUOTING ANY SHARE FROM THIS. The comparison covers only the vaults where we hold BOTH an advertised rate and a realised one, whagent_changesread-onlyWhat moved in the agent record, across every agent, since a date. The counterparty check answers what is true about one address NOW; this answers what changed, for all of them, which is the question anybody holding a liscounterparty_bulkCheck up to fifty addresses in one call, each with its observations, AND what the set shares underneath: the parties that two or more of them pay. That second part is the one answer no per-address row can contain, becausagent_dependenciesIf 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 more than one of them pays. THE PRODUCT IS THE DISTINCTION, NOT THE JOIN: findinagent_businessDoes this agent have a BUSINESS, and can any of it be demonstrated? Six questions an investor, a marketplace or an operator actually asks, each answered separately: are the addresses paying it really independent customeragent_economic_profileOne agent, four readings, in the order a buyer actually asks them: what it EARNS and from whom, whether its contracted work FINISHED and who signed it off, who it RESTS ON as a supplier, and whether it is still TRADING aexit_screenYOU 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 question across every vault whose withdrawal history we have read, which is the quevault_exit_confidenceBefore 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 about return or about risk of loss; this is about the practical question a holde
…and 20 more.
Connect it
claude mcp add --transport http aspern-counterparty-checks-for-agents https://aspern.org/mcpSettings → Connectors → Add custom connector
URL: https://aspern.org/mcp{
"mcpServers": {
"aspern-counterparty-checks-for-agents": {
"url": "https://aspern.org/mcp"
}
}
}{
"servers": {
"aspern-counterparty-checks-for-agents": {
"type": "http",
"url": "https://aspern.org/mcp"
}
}
}Questions
What does ASPERN: counterparty checks for agents do?
What the chain records about an address before you pay it, and whether a payment fits it. It exposes 60 tools to AI assistants.
What tools does ASPERN: counterparty checks for agents provide?
60 tools, including identify, check_service_endpoint, preflight_payment, vault_assessment, vault_exits, vault_risk_dimensions, portfolio_screen, capital_coverage, exit_lifecycle_coverage, endpoint_coverage, payment_evidence, evidence_for….
How do I connect ASPERN: counterparty checks for agents to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://aspern.org/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does ASPERN: counterparty checks for agents require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is ASPERN: counterparty checks for agents online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes ASPERN: counterparty checks for agents?
aspern.org. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Finance & Payments
-
TipRanksOnlineOfficial
Live TipRanks market data: analyst ratings, Smart Score, technicals, options, portfolios.
-
GoCardless MCP ServerOnline · sign-in requiredOfficial
Manage GoCardless payments, mandates, subscriptions, refunds and payouts via AI assistants.
-
Avalara AvaTaxOnline · sign-in requiredOfficial
Access Avalara AvaTax API for tax calculation, transactions, nexus management, and compliance
-
Avalara ReturnsOnline · sign-in requiredOfficial
Provides access to Avalara Global Returns API for tax returns, filing calendars, and compliance data
-
Avalara Tax ContentOnline · sign-in requiredOfficial
Provides access to Avalara Tax Content: TTE configs, jobs, communications, lodging, autorental
-
Avalara Tax Registrations and Business LicensesOnline · sign-in requiredOfficial
Provides access to Avalara Tax Registration and Business Licenses APIs for filings and registrations