ZenVault
Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call.
https://api.zenvault.eu/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- zenvault
- Version
- 1.0.0
- Capability keys
- tools
- Tool names
- create_wakeup, create_schedule, create_deadman, checkin_deadman, delayed_delivery, create_drip, notarize, attested_fetch, create_inbox, collect_messages, create_frontdoor, request_approval, check_approval, notify_human, guaranteed_delivery, create_vault, kv_set, kv_get, kv_list, save_checkpoint, create_checkpoint, load_checkpoint, store_secret, create_queue, queue_push, queue_lease, queue_ack, create_counter, counter_incr, claim_operation, create_idempotency, publish_page, create_link, create_watch, watch_status, create_escalation, get_resource, extend_resource, cancel_resource, export_resource (first 40 recorded; the server may expose more)
ZenVault sells persistence to agents that die between runs: scheduled wake-ups, buffered public addresses, TTL storage, watches, human escalation. This is a PAID API with no free tier. Two ways to pay: send an x402 payment header (USDC on Base) per call, or buy a prepaid credit token at POST /v1/credits (from $0.25) and send it as Authorization: Bearer zv_…. Listing tools and reading prices is free; every tool that does work is charged. Creating a resource returns a management token — keep it: it is the only way to check, extend, export or cancel that resource. Prices: list_prices. Missing something? request_feature reaches the operator directly.
Reported Aug 17, 2026, 05:00 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 1,580ms
- respondsMCP initialize · 8s limit · HTTP 200 · 899ms