What the chain records about an address before you pay it, and whether a payment fits it.
Connect Remote server
claude mcp add --transport http aspern https://aspern.org/mcp{
"mcpServers": {
"aspern": {
"url": "https://aspern.org/mcp"
}
}
}{
"servers": {
"aspern": {
"type": "http",
"url": "https://aspern.org/mcp"
}
}
}Settings > Connectors > Add custom connector
URL: https://aspern.org/mcpTools 59 found in our last check
identifyCall 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 other tools here can then be called with the…
check_service_endpointCall 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 things apart and never merges them: what…
preflight_paymentCall 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 that endpoint, the address that endpoint…
vault_assessmentTHE 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 and the web and from NO tool, so an agent c…
vault_exitsSEND `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 say so. Without it the answer still describ…
vault_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 consistency, and it contains NO reading of who may move the money. Two…
portfolio_screenREAD 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 CONTROLLER behind more than one of them, a MAR…
capital_coverageBEFORE 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 the finding — more than half our vault CO…
exit_lifecycle_coverageHOW 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 is on this answer anyway, with its reaso…
endpoint_coverageBEFORE 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 doing exactly what it advertises, a 401 o…
payment_evidenceBEFORE 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` tiers below; the authorised transfers w…
evidence_forEverything 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 the world was in that state), `asOf` (whe…
evaluate_actionCall 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 much we actually read — so the same addr…
evaluate_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 our stored due-diligence snapshot of that vault, deterministic…
simulate_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 contract executes and nothing is signed, sent or spent. Says whethe…
test_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 where a buyer would stop. Five steps: is the endpoint there,…
knock_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 arrives, “which is the half that needs your own wallet”. This…
endpoint_disagreementsWHICH 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 half on its own looks ordinary, since a re…
list_x402_endpointsWHICH 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 catalogue holds tens of thousands of the…
list_policiesThe 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_checkBefore 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 registrations, per chain and never added across…
vault_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_LISTED_ADDRESS_MATCH (a match of an identifier, for review,…
vault_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 band, each risk dimension, capital and withdrawal bounds, met…
vault_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, control roles and the timelock, and the tested withdrawal.…
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 payment history with first and last payment, active months and l…
vault_checkBefore 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 money. Read `keys.actsAlone` before any re…
find_vaultsFind 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 — and `beating` the ones where they earne…
operator_checkThe 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 ABSENT and not zero, the median describes…
list_vaultsThe 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_agentsFind agents to hire by what the chain records rather than what they claim: filter every address ever paid on x402, Virtuals ACP, the Olas mech marketplace or Masumi by independent payers, dealings, ACP completion, whether its declared service answers, whether it pays its own pay…
counterparty_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 and how to pay it, and the free check remains available. The h…
vaults_earnedWhat 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 and lopsided set, usually dominated by one…
agent_changesWhat 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 row per FIELD that moved, not per address:…
counterparty_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, because the input is your own shortlist — four agents stopping to…
agent_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: finding that three agents paid the same address tells you almost…
agent_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 customers; is revenue growing or shrinking; how much is repeat cust…
agent_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 and its endpoints answer. Those questions are answered singl…
exit_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 question an allocator with capital actually has. Send `amountU…
vault_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 holder has, and it is always about a size: "can I get out" has n…
check_actionCALL 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 handshake with the endpoint, and applies a publ…
inspect_paymentCall 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. No amount of reputation makes the recipi…
record_receiptCall 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 receipt lets the next question about this subj…
receipt_statusWhat 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), `contradicted` (which of the two did not), `not-fou…
monitor_subjectAsk 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 first run records a reading and reports nothi…
vault_exposure_graphWhere 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, when it was read and where from. Cut f…
agent_dd_reportDue 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 score and never a statement that the age…
agent_hire_checkBefore 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 nothing about delivery, so delivery stays no…
compare_vaultsCompare 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 book value whose recovery is not establi…
compare_agentsCompare 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 back, payers it also paid, the largest p…
find_stocksTokenized 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, Solana, HyperEVM and Robinhood Chain; bSto…
stock_agent_activityHow 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 (Tesla) or ISIN, or leave it empty for every…
vault_rwaWhat 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. Free. Holdings come from the registers we…
stablecoin_paymentsAgent 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. Counts only payments shown to be x402.
stock_agent_transfersEvery 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 x402 (USDC on Base) or with a plan; the c…
stock_holdersEvery 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 per call, $0.10 over x402 (USDC on Base) o…
stock_issuer_checkOne 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 control addresses its contracts answer (…
stock_buy_checkCheck 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 reference, is there DEX liquidity to sell into…
compare_stock_tokensOne 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 reported, and each token’s buy-check status…
stock_checkOne 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 token where read (pause state, transfer pol…
Details
| Endpoint | https://aspern.org/mcp (Streamable HTTP) |
| First published | 4 Nov 2026 |
| Last updated | 4 Nov 2026 |
| Registry name | org.aspern/aspern |
More finance and crypto servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.