# eu.zenvault/zenvault Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.0.2 - **Author:** eu.zenvault - **License:** Unknown - **Endpoints:** streamable-http https://api.zenvault.eu/mcp - **Source:** https://zenvault.eu - **Endpoint health:** reachable (last checked 2026-09-22T05:23:57.025Z, 5 samples) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-22T05:23:57.025Z - **Version scanned:** live - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. ## Tools 44 declared. Observed from a live `tools/list` probe. - `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. - …and 4 more ## Install **Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"zenvault\": {\n \"type\": \"http\",\n \"url\": \"https://api.zenvault.eu/mcp\"\n }\n }\n}" ``` ## Blast radius Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface. - Floor 9, ceiling 27 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/eu.zenvault%2Fzenvault - Install plan: https://forgeregistry.com/api/v1/packages/eu.zenvault%2Fzenvault/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/eu.zenvault%2Fzenvault - HTML page: https://forgeregistry.com/registry/eu.zenvault%2Fzenvault - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.