Skip to content

Early access Governed MCP calls open to beta partners in March 2027. The MCP tracker and scanner are free to use today.

org.aspern/aspern MCP server

Community server, not reviewed by Stackduke

40 tools · tools last listed 4 Nov 2026

A community server in the official MCP registry. Once a day, Stackduke's Radar connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.

Address
https://aspern.org/mcp
Tracked since
16 Oct 2026
Tools first listed
16 Oct 2026
Tools last listed
4 Nov 2026

All 40 tools

By label: 2 that move or spend money, 2 that delete or destroy things, 1 that sends or publishes, 14 that create or change things, 21 said to only read.

ToolLabelled as
check_actionMoves money
evaluate_actionMoves money
exit_screenDeletes
vault_exitsDeletes
vault_assessmentSends
agent_businessChanges things
agent_dependenciesChanges things
agent_economic_profileChanges things
counterparty_bulkChanges things
counterparty_historyChanges things
evaluate_vault_decisionChanges things
inspect_paymentChanges things
knock_on_endpointChanges things
monitor_subjectChanges things
record_receiptChanges things
simulate_withdrawalChanges things
test_purchaseChanges things
vault_exit_confidenceChanges things
vault_risk_dimensionsChanges things
agent_changesSaid to only read
capital_coverageSaid to only read
check_service_endpointSaid to only read
counterparty_checkSaid to only read
endpoint_coverageSaid to only read
endpoint_disagreementsSaid to only read
evidence_forSaid to only read
exit_lifecycle_coverageSaid to only read
find_agentsSaid to only read
find_vaultsSaid to only read
identifySaid to only read
list_policiesSaid to only read
list_vaultsSaid to only read
list_x402_endpointsSaid to only read
operator_checkSaid to only read
payment_evidenceSaid to only read
portfolio_screenSaid to only read
preflight_paymentSaid to only read
receipt_statusSaid to only read
vault_checkSaid to only read
vaults_earnedSaid to only read

Labels for community servers are machine guesses from each server's own tool names, descriptions and hints (accuracy not yet measured). They are not a safety verdict. How labels work

Recent checks

Listed its tools at 19 of 19 checks in the 30 days to 4 Nov 2026

Recent changes

  1. Description rewritten on counterparty_check, vault_check, vault_exits. Inputs or outputs changed on knock_on_endpoint, vault_check, vault_exits.

  2. 1 tool added: simulate_withdrawal. Inputs or outputs changed on vault_check. Counted as able to do more: simulate_withdrawal (create or change things).

  3. Inputs or outputs changed on evaluate_vault_decision, knock_on_endpoint, vault_check.

  4. 1 tool added: evaluate_vault_decision. Counted as able to do more: evaluate_vault_decision (create or change things).

  5. Description rewritten on vaults_earned. Inputs or outputs changed on find_vaults, list_vaults, vault_check, vault_exits, vaults_earned.

Show 5 earlier changes
  1. Description rewritten on agent_business, evaluate_action, find_agents, knock_on_endpoint, preflight_payment. Inputs or outputs changed on agent_business, agent_economic_profile, evaluate_action, find_agents, knock_on_endpoint and 3 more.

  2. Inputs or outputs changed on agent_changes, check_action, find_agents.

  3. 2 tools added: payment_evidence, receipt_status. Description rewritten on record_receipt. Inputs or outputs changed on agent_business, counterparty_check, inspect_payment, preflight_payment, record_receipt and 1 more.

  4. Description rewritten on knock_on_endpoint. Inputs or outputs changed on knock_on_endpoint.

  5. 2 tools added: endpoint_coverage, exit_lifecycle_coverage. Inputs or outputs changed on counterparty_check, vault_exits.

A change is a tool added, removed or rewritten between two daily checks. Radar keeps each server's latest 10. What counts as a change

Want a say before an agent uses tools like these?

Stackduke is building an approval gateway that will hold an agent's risky tool calls until a person approves them.

Join the waitlist