Home / MCP registry index / org.aspern/aspern
ASPERN: counterparty checks for agents
org.aspern/aspern in the official MCP registry.
Endpoint https://aspern.org/mcp. Source: github.com/aspern-org/aspern-docs.
The registry describes it as: What the chain records about an address before you pay it, and whether a payment fits it.
On 2026-10-30 we read its 39 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
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 evaluate_action evaluate_vault_decision test_purchase knock_on_endpoint endpoint_disagreements list_x402_endpoints list_policies counterparty_check vault_check find_vaults operator_check list_vaults find_agents counterparty_history vaults_earned agent_changes counterparty_bulk agent_dependencies agent_business agent_economic_profile exit_screen vault_exit_confidence check_action inspect_payment record_receipt receipt_status monitor_subject
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/org-aspern-aspern)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.