ASPERN: counterparty checks for agents
What the chain records about an address before you pay it, and whether a payment fits it
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: detect fraudulent transactions.Similar tools
Listed for the same task: detect fraudulent transactionsReviews
No review yet. Used ASPERN: counterparty checks for agents? Be the first to help others choose.What it does
ASPERN: counterparty checks for agents is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: payments. That makes it a candidate for tasks such as detect fraudulent transactions or buy products online.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://aspern.org/mcpstreamable-http
In Claude Code: claude mcp add --transport http aspern https://aspern.org/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"aspern": {
"url": "https://aspern.org/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE ASPERN: counterparty checks for agents answered an MCP connection on 15 Nov 2026 and introduced itself as aspern 1.3.0 (MCP protocol 2025-06-18).
59 tools offered to AI assistants
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-8004 registration number and it says which party that is, with the evidence for the link, so the othercheck_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 probe reached it, what it answered with, and how many of the last readings answered. It keeps three tpreflight_payment· Call 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 themselves published for tvault_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 publish on chain under their own name. Until 2026-10-21 this document was reachable from the API andvault_exits· SEND `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 sentence did not sayvault_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, which it is not: ours weighs drawdown, crowding, exit, concentration and consistency, and it contains NOportfolio_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 answers the three questions that only exist across holdings and that no vault page can show you: a CONTROLcapital_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: by number of open vaults and by the capital in them. They differ by a lot, and the difference is thexit_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 aside to claim, money that actually left, and an attempt that failed — and we read THREE. The fourth iendpoint_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 states mean different things and summing them produces a figure about nothing: a 402 is an x402 seller dopayment_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 figures that NEST and are never added up (x402 counts only the `protocol`, `route` and `facilitator`evidence_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 just make one, or to see what is MISSING before you act. Every edge has `source`, `observedAt` (when th
Show 47 more
evaluate_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 put capital into a vault. The answer depends on the AMOUNT, the ACTION, the POLICY you name and how mevaluate_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 it must stay inside and the CLAIMS the decision rests on. It is judged against our stored due-diligencsimulate_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 the holder you name or, if you name none, as its largest depositor: the contract executes and nothintest_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 that objects. All five are asked in one pass and in that order, so the walk stops where a buyer would stknock_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 caveat has always said that only paying and reading the answer establishes what arrives, “which is theendpoint_disagreements· WHICH 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 held together: either hallist_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 this a caller had to know its URL by heart. Nearly every catalogued resource names a payee, and the clist_policies· The 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 correct. Free.counterparty_check· Before 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, Olas tasks and registravault_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 only, with the list version and whether it is current. Paid ($0.01). States: EXACT_LISTED_ADDRESS_MATCHvault_due_diligence· The 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 band, each risk dimensvault_drift· What 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, control roles and thcounterparty_evidence· Before 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 payment history with firsvault_check· Before 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`: who can move the monfind_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 where a holder earned LESS than the venue advertises — how many there are is in the answer, never here —operator_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 travel inside it: the leader’s holding is readable on Hyperliquid and Drift ONLY, so elsewhere it is ABlist_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 read that vault, never that it does not exist.find_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. MOST ARE NOT SHOWN TO BE AI AGENTS: every row is a paid on-chain service, and `subject.serviceKind` scounterparty_history· How 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 and how to pay it, andvaults_earned· What 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, which is a narrow andagent_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 answers what changed, for all of them, which is the question anybody holding a list asks next. One rowcounterparty_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 them pay. That second part is the one answer no per-address row can contain, because the input is youragent_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 more than one of them pays. THE PRODUCT IS THE DISTINCTION, NOT THE JOIN: finding that three agentsagent_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, each answered separately: are the addresses paying it really independent customers; is revenue growinagent_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 who signed it off, who it RESTS ON as a supplier, and whether it is still TRADING and its endpoints ansexit_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 question across every vault whose withdrawal history we have read, which is the question an allocator wvault_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 about return or about risk of loss; this is about the practical question a holder has, and it is alwcheck_action· CALL THIS BEFORE YOUR AGENT SIGNS ANYTHING THAT MOVES MONEY. One request instead of five: it reads the counterparty record, decodes the calldata you are about to sign, looks up the seller’s own catalogue listing, runs an unpaid 402 handshakinspect_payment· Call this with the CALLDATA you are about to sign, before you sign it. Every other check here asks whether an address is worth dealing with; this asks whether the transaction is the one you think it is, and the two catch different losses. Nrecord_receipt· Call this AFTER you have paid an address or called a tool, to put what you did on the record. Until now this platform answered "should I" and never heard what happened, which is the difference between a lookup and a control layer: a receiptreceipt_status· What became of a receipt you recorded with `record_receipt`. We do not take a receipt on your word: each one is read against the payments WE read from the chain and judged `verified` (it paid the subject and the amount agrees), `contradictemonitor_subject· Ask to be told when the answer about an address CHANGES. The dimensions are the ones the counterparty check already answers, so this is that same reading on a schedule rather than a second opinion; what it adds is the comparison. The firstvault_exposure_graph· Where one vault’s capital is exposed, as a graph: vault → market → collateral, loan asset and oracle. Every edge carries its size in dollars, its share of what the vault allocates, the vault’s share of the market, the LLTV where it secures,agent_dd_report· Due diligence on an ACP provider before hiring it: does it finish the work, who said the work was done, who pays it, is the record current, who is behind it, is it on a sanctions list. Each answer has a status and what would settle it. No sagent_hire_check· Before the first payment to an agent over x402: does its endpoint answer, does it charge what it lists, who pays it, does it deliver. Each answer is ok, caution or not_established, with what would settle it. x402 records a payment and nothicompare_vaults· Compare 2 to 5 named vaults side by side on one taxonomy: identity (chain, address, platform, curator, operator), capital (reported assets, the venue’s withdrawable figure, the withdrawable share, and what the capital figure means, e.g. a bcompare_agents· Compare 2 to 5 agent addresses side by side on one taxonomy, from the record we keep for every paid address: identity (registered name, ERC-8004 registrations, rails, chains), custom (counterparties, independent payers who were never paid bfind_stocks· Tokenized stocks on chain, one row per company across every issuer and network we read (Coinbase on Base; Robinhood on Robinhood Chain; xStocks on Solana, Ethereum, Arbitrum, BNB Chain, TON, Tron and others; Ondo on Ethereum, BNB Chain, Solstock_agent_activity· How many AI agents moved a tokenized stock over a window you choose (default the last 24 hours): distinct agent addresses, transfers in and out, value at the issuer’s reference, by token and network. Ask by ticker (TSLA), company name (Teslvault_rwa· What one vault holds in real-world assets: tokenized stocks it holds at its own address, what it has lent against tokenized stocks as collateral (exposure through borrowers, not stocks it owns), and whether its own asset is a stablecoin. Frstablecoin_payments· Agent payments in stablecoins over a window you choose (default the last 24 hours): how many x402 payments, from how many paying addresses to how many receiving ones, by token and network. Filter by stablecoin (USDC) or network. Free. Countstock_agent_transfers· Every transfer of a tokenized stock that touched an agent address over a window: the agent and its roles, the token, in or out, the amount and its value, the time and the transaction, newest first (up to 5,000). PAID per call, $0.10 over x4stock_holders· Every holder of one tokenized stock, from the register rebuilt from its transfers since deployment: balance, value at the issuer’s reference, share outside the issuer’s own wallets, and transfer counts, largest first (up to 2,000). PAID perstock_issuer_check· One issuer of tokenized stocks (coinbase, robinhood, xstocks, ondo, bstocks, dinari): the entity and jurisdiction as its documents name them, what it has tokenized (tokens, companies, value at its reference values), on which networks, the cstock_buy_check· Check a tokenized stock BEFORE BUYING it, by its contract (or Solana mint) and network: can it be moved today (pause state, a permanent delegate), is a controlling address on the OFAC SDN list, does the pool price track the issuer’s referencompare_stock_tokens· One company’s tokenized stock SIDE BY SIDE across issuers and networks, by ticker, company name or ISIN: supply, value at the issuer’s reference, pool premium, DEX liquidity, pause state, holders and the largest holder, reserves where reporstock_check· One tokenized stock by its contract address (EVM) or mint (Solana): the issuer, the network, supply (read on chain except Coinbase’s), the issuer’s reference value with its source and time, what is in issue in dollars, who controls the toke
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Repository | https://github.com/aspern-org/aspern-docs | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Version | 1.3.0 | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Hosted endpoint | https://aspern.org/mcp | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Website | https://aspern.org | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 20h ago |
Change history
- VERSION04 Nov 20261.2.0 → 1.3.0
- VERSION30 Oct 20261.1.0 → 1.2.0
- VERSION20 Oct 20261.0.0 → 1.1.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is ASPERN: counterparty checks for agents still online?
Free alerts · no account▲ 0Do you run ASPERN: counterparty checks for agents? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about ASPERN: counterparty checks for agents
How do I connect ASPERN: counterparty checks for agents?
Use the hosted endpoint https://aspern.org/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does ASPERN: counterparty checks for agents offer?
When Electra Index connected on 15 Nov 2026, it listed 59 tools: identify, check_service_endpoint, preflight_payment, vault_assessment, vault_exits, vault_risk_dimensions, portfolio_screen, capital_coverage and more. The full list is in "Live check" above.
Is ASPERN: counterparty checks for agents online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use ASPERN: counterparty checks for agents for?
Based on its description, it is most relevant to: detect fraudulent transactions, buy products online, handle refund requests, reconcile payments.