# Aspern MCP server

Source: https://glimind.com/server/mcp-registry%2Forg.aspern%2Faspern
Registry id: `mcp-registry/org.aspern/aspern`
Status: live (checked 2026-10-26T22:34:23.718Z)

## Verdict

Aspern MCP server answered 99.32% of Glimind's liveness checks over 30 days, better than 12% of MCP servers, with 1022 ms median handshake and 26 outages in 90 days. Its agent-readiness grade is A (96/100) across 38 tools, costing an agent about 12,689 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.32% | 12% of MCP servers |
| Median handshake latency | 1022 ms | 20% of MCP servers |
| p95 handshake latency | 3633 ms | — |
| Checks in 30 days | 5,006 | — |
| Outages, 90 days | 26 | — |
| Median recovery | 8 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 38 | — |
| Tool-list size for an agent | ~12,689 tokens | 15% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "aspern-mcp-server": {
      "type": "http",
      "url": "https://aspern.org/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http aspern-mcp-server https://aspern.org/mcp
```

## Tools (38)

- `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, each answered separat
- `agent_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, 
- `agent_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 the
- `agent_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 
- `capital_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 v
- `check_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 t
- `check_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, wha
- `counterparty_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 p
- `counterparty_check`: Before paying or hiring an agent: what the chain records about that address. Independent payers (counterparties that paid it and were never paid back), the ones
- `counterparty_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 th
- `endpoint_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 thi
- `endpoint_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
- `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 va
- `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 se
- `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 aside to claim, money 
- `exit_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 v
- `find_agents`: Find 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 Ma
- `find_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 LES
- `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 numb
- `inspect_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 t
- `knock_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 
- `list_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 eva
- `list_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
- `list_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 
- `monitor_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 s
- `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 l
- `payment_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
- `portfolio_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 question
- `preflight_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 wha
- `receipt_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
- `record_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 h
- `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 that objects. All five a
- `vault_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 unde
- `vault_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 ris
- `vault_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 abou
- `vault_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, an
- `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, which it is not: ours we
- `vaults_earned`: What depositors actually KEPT, against what their vault advertised. READ `population` BEFORE QUOTING ANY SHARE FROM THIS. The comparison covers only the vaults 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.