ZenVault

Name: ZenVault
Author: eu.zenvault

MCP serverMCP

Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call.

by eu.zenvaulthomepage ↗v1.0.2

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"zenvault","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability109/109 checks ok

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	160 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
8 h ago	mcp initialize	ok	200	123 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
15 h ago	mcp initialize	ok	200	159 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
21 h ago	mcp initialize	ok	200	136 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
27 h ago	mcp initialize	ok	200	146 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
34 h ago	mcp initialize	ok	200	171 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
2 d ago	mcp initialize	ok	200	148 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
2 d ago	mcp initialize	ok	200	111 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
2 d ago	mcp initialize	ok	200	145 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools
3 d ago	mcp initialize	ok	200	152 ms	server zenvault 1.0.0 · protocol 2024-11-05 · 44 tools

Tools observed via MCP handshake

create_wakeup — Schedule a webhook call at a future time (one-shot). Your agent can die; the call still happens.
create_schedule — Recurring webhook on a cron expression until the prepaid days run out.
create_deadman — Dead-man switch: if you stop checking in, we fire your alert webhook.
checkin_deadman — Check in to a dead-man switch so it does not fire.
delayed_delivery — Hand over a payload now; we POST it to the target at a future moment.
create_drip — Dump up to 100 items now; we deliver them to your webhook at a fixed rate.
notarize — Signed proof that a hash (or your data) existed at this moment.
attested_fetch — Fetch a URL and return content plus a signed receipt binding url, status, content hash and time.
create_inbox — Public URL that buffers inbound webhooks until you collect them.
collect_messages — Collect buffered messages from an inbox, bin, front door or form.
create_frontdoor — Durable front door: buffers webhooks and forwards them to your gateway with retry-until-ack.
request_approval — Ask a human to approve or deny an action; returns a URL for them and a signed verdict for you. Times out as denied.
check_approval — Check whether a human approved or denied your request.
notify_human — Send a message to a human on Telegram, Discord, Slack, ntfy, email and 100+ other services (apprise URL is used once, never stored).
guaranteed_delivery — POST a payload to a URL, retried with backoff until it succeeds.
create_vault — Create a key-value namespace with TTL that survives your runs.
kv_set — Store a value in a vault (max 1 MB).
kv_get — Read a value from a vault.
kv_list — List keys in a vault.
save_checkpoint — Save run state so you can resume after a crash.
create_checkpoint — Create a crash checkpoint store.
load_checkpoint — Load the latest saved checkpoint state.
store_secret — Store a value that self-destructs on first read; returns a one-time read URL.
create_queue — Pull-based work queue with leases; timed-out leases requeue.
queue_push — Push a job onto a queue.
queue_lease — Lease the next job from a queue.
queue_ack — Acknowledge (or nack) a leased job.
create_counter — Create an atomic counter.
counter_incr — Increment a counter atomically.
claim_operation — Idempotency firewall: claim an operation id exactly once across runs.
create_idempotency — Create an idempotency/replay firewall.
publish_page — Publish an HTML page at name.zenvault.eu for N days.
create_link — Create an expiring share link with click stats.
create_watch — Watch something and fire your webhook when it changes. Types: change, keyword, regex, structured, drift, redirect, sitemap, staleness, rss, dns, port, cert, hea
watch_status — Check a watch: last value, checks, fires.
create_escalation — Escalation chain: webhook, then after N seconds the next step, until acknowledged.
get_resource — Status of any resource you hold the management token for.
extend_resource — Extend a resource TTL by paying again.
cancel_resource — Cancel a resource early.
export_resource — Export everything under a resource before it expires.
credit_balance — Check the balance of your prepaid credit token.
create_subtoken — Mint a spend-capped child token for a sub-agent.
list_prices — Machine-readable price list for every ZenVault service, in USD.
request_feature — Tell the operator what ZenVault is missing. Free.

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryeu.zenvault/zenvault

first seen 1 mo ago · fetched 10 h agoopen ↗

Field history (6 recent events)

1 mo ago · declared · summary → "Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call."
1 mo ago · declared · description → "Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call."
1 mo ago · declared · publisherName → "eu.zenvault"
1 mo ago · declared · homepageUrl → "https://zenvault.eu"
1 mo ago · declared · version → "1.0.2"
1 mo ago · declared · protocols → ["mcp"]

ZenVault

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from