Index / MCP servers / ASPERN: counterparty checks for agents

ASPERN: counterparty checks for agents MCP server

Connect ASPERN: counterparty checks for agents and your agent gets 59 tools, among them agent_business, agent_changes, agent_dd_report. It answers at https://aspern.org/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 25 September 2026; the last check, on 8 November 2026, succeeded.

Status
Answering
Tools
59
Official
yes, served from aspern.org
Reliability
4 of 4 checks
Response time
91 ms
Transport
streamable HTTP
Last checked
8 November 2026

What the chain records about an address before you pay it, and whether a payment fits it.

Description as the publisher wrote it.

The 59 tools ASPERN: counterparty checks for agents offers

ToolWhat it does
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 growin
Inputs: address
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
Inputs: since, address, limit, offset
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 s
Inputs: address
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
Inputs: addresses
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 ans
Inputs: address
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 nothi
Inputs: address
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 th
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 handshak
Inputs: action, recipient, subject, chain, from, valueWei
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 t
Inputs: url
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 b
Inputs: addresses, sort, order
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 repor
Inputs: q
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 b
Inputs: slugs, sort, order
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
Inputs: addresses
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 registra
Inputs: address
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 firs
Inputs: address
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
Inputs: address, days
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 do
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 hal
Inputs: limit
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 m
Inputs: action, subject, amountUsd, chain, resource, policy
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-diligenc
Inputs: vault, action, amountUsd, mandate, claims, rationale
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 th
Inputs: subject
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 i
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 w
Inputs: amountUsd, limit
find_agentsFind 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` s
Inputs: rail, minIndependent, minDealings, minCompletion, minOutcomeCoverage, activeDays
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, Sol
Inputs: kind, q, chain, limit
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 —
Inputs: earned, maxRisk, minOwnShare, chain, platform, agentManaged
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
Inputs: q
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. N
Inputs: data, to, resource, maxQuoteAgeSeconds, refreshQuote, expect
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
Inputs: resource, payment, asset, fill, query, send
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.
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.
Inputs: q, limit, offset
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 c
Inputs: payee, q, limit
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
Inputs: subject, dimensions, policy
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 AB
Inputs: slug
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`
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 CONTROL
Inputs: holdings
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 t
Inputs: to, amountUsd, chain, resource
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), `contradicte
Inputs: id
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
Inputs: subject, action, reference, chain, amountUsd, expected
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 nothin
Inputs: vault, amountUsd, holder, pass
19 more tools

stablecoin_payments, stock_agent_activity, stock_agent_transfers, stock_buy_check, stock_check, stock_holders, stock_issuer_check, test_purchase, vault_assessment, vault_check, vault_drift, vault_due_diligence, vault_exit_confidence, vault_exits, vault_exposure_graph, vault_risk_dimensions, vault_rwa, vault_sanctions_screening, vaults_earned

Add ASPERN: counterparty checks for agents to your AI client

Every block below points at https://aspern.org/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http aspern-counterparty-checks-for-a https://aspern.org/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://aspern.org/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "url": "https://aspern.org/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "aspern-counterparty-checks-for-a": {
      "type": "http",
      "url": "https://aspern.org/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "aspern-counterparty-checks-for-a": {
      "url": "https://aspern.org/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "serverUrl": "https://aspern.org/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "url": "https://aspern.org/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: ASPERN: counterparty checks for agents
version: 0.0.1
schema: v1
mcpServers:
  - name: ASPERN: counterparty checks for agents
    type: streamable-http
    url: https://aspern.org/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "httpUrl": "https://aspern.org/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "type": "http",
      "url": "https://aspern.org/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "aspern-counterparty-checks-for-a": {
      "url": "https://aspern.org/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Faspern.org%2Fmcp&type=streamable_http&id=aspern-counterparty-checks-for-a&name=ASPERN%3A%20counterparty%20checks%20for%20agents

Is ASPERN: counterparty checks for agents up right now?

It answered our last check on 8 November 2026 in 91 ms. Over 4 checks since 25 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to ASPERN: counterparty checks for agents

Questions about ASPERN: counterparty checks for agents

Is there an official ASPERN: counterparty checks for agents MCP server?

Yes. It is published by aspern.org and served from aspern.org, the vendor's own domain: https://aspern.org/mcp.

How many tools does ASPERN: counterparty checks for agents have?

59, as returned by the server's own tools/list on 15 November 2026: agent_business, agent_changes, agent_dd_report, agent_dependencies, agent_economic_profile, agent_hire_check, capital_coverage, check_action, and 51 more.

Is ASPERN: counterparty checks for agents down?

It answered our last check on 8 November 2026 in 91 ms. Over 4 checks since 25 September 2026 it answered 4.

How do I add ASPERN: counterparty checks for agents to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://aspern.org/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does ASPERN: counterparty checks for agents need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: org.aspern. Endpoint host: aspern.org. ARD identifier: urn:air:org.aspern:mcp:aspern. First indexed 25 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.