Skip to content

ZenVault MCP server

eu.zenvault/zenvaultzenvault.eustreamable-httpv1.0.2Scanned

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

36 tools: 1 can delete or cancel things, 29 change things and 6 only read.

Tools: 1 delete, 0 irreversible, 29 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 7
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ZenVault MCP server can do

The ZenVault MCP server is published by zenvault.eu, a domain the MCP Registry verified. It has 36 tools. It can delete or cancel things (1 tool: cancel_resource) and create or change data (29 tools: create_wakeup, create_schedule, create_deadman, checkin_deadman and 25 more). 6 tools only read.

2 tools read private data (kv_get and kv_list); 1 tool brings in text other people can write (attested_fetch); 7 tools can send data out of your system (create_wakeup, create_schedule, create_deadman and 4 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

36 tools

Deletes or cancels 1Claude Code: deny
  • cancel_resourceCancel a resource early.No findings

    Why it is in this group

    • The name "cancel_resource" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel a resource early.
Changes things 29Claude Code: ask
  • checkin_deadmanCheck in to a dead-man switch so it does not fire.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check in to a dead-man switch so it does not fire.
  • claim_operationIdempotency firewall: claim an operation id exactly once across runs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Idempotency firewall: claim an operation id exactly once across runs.
  • collect_messagesCollect buffered messages from an inbox or bin.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Collect buffered messages from an inbox or bin.
  • counter_incrIncrement a counter atomically.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Increment a counter atomically.
  • create_binRequest bin: a public URL that captures every request in full (method, headers, body) for debugging webhooks.No findings

    Why it is in this group

    • The name "create_bin" says "create": a word for a change.
    Description, as the server wrote it
    Request bin: a public URL that captures every request in full (method, headers, body) for debugging webhooks. Watch it live at https://api.zenvault.eu/view.
  • create_checkpointCreate a crash checkpoint store.No findings

    Why it is in this group

    • The name "create_checkpoint" says "create": a word for a change.
    Description, as the server wrote it
    Create a crash checkpoint store.
  • create_counterCreate an atomic counter.No findings

    Why it is in this group

    • The name "create_counter" says "create": a word for a change.
    Description, as the server wrote it
    Create an atomic counter.
  • create_deadmanDead-man switch: if you stop checking in, we fire your alert webhook.Can send data outNo findings

    Why it is in this group

    • The name "create_deadman" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Dead-man switch: if you stop checking in, we fire your alert webhook.
  • create_escalationEscalation chain: webhook, then after N seconds the next step, until acknowledged.No findings

    Why it is in this group

    • The name "create_escalation" says "create": a word for a change.
    Description, as the server wrote it
    Escalation chain: webhook, then after N seconds the next step, until acknowledged.
  • create_idempotencyCreate an idempotency/replay firewall.No findings

    Why it is in this group

    • The name "create_idempotency" says "create": a word for a change.
    Description, as the server wrote it
    Create an idempotency/replay firewall.
  • create_inboxPublic URL that buffers inbound webhooks until you collect them.No findings

    Why it is in this group

    • The name "create_inbox" says "create": a word for a change.
    Description, as the server wrote it
    Public URL that buffers inbound webhooks until you collect them.
  • create_queuePull-based work queue with leases; timed-out leases requeue.No findings

    Why it is in this group

    • The name "create_queue" says "create": a word for a change.
    Description, as the server wrote it
    Pull-based work queue with leases; timed-out leases requeue.
  • create_scheduleRecurring webhook on a cron expression (at most every 15 minutes), for up to 30 days, renewable for free.Can send data outNo findings

    Why it is in this group

    • The name "create_schedule" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Recurring webhook on a cron expression (at most every 15 minutes), for up to 30 days, renewable for free.
  • create_vaultCreate a key-value namespace with TTL that survives your runs.No findings

    Why it is in this group

    • The name "create_vault" says "create": a word for a change.
    Description, as the server wrote it
    Create a key-value namespace with TTL that survives your runs.
  • create_wakeupSchedule a webhook call at a future time (one-shot).Can send data outNo findings

    Why it is in this group

    • The name "create_wakeup" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Schedule a webhook call at a future time (one-shot). Your agent can die; the call still happens.
  • create_watchWatch something and fire your webhook when it changes.Can send data outNo findings

    Why it is in this group

    • The name "create_watch" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Watch something and fire your webhook when it changes. Types: change, keyword, regex, structured, drift, redirect, sitemap, staleness, rss, dns, port, cert, heartbeat.
  • delayed_deliveryHand over a payload now; we POST it to the target at a future moment.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Hand over a payload now; we POST it to the target at a future moment.
  • export_resourceExport everything under a resource before it expires.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Export everything under a resource before it expires.
  • extend_resourceExtend a resource lifetime, free, up to 30 days ahead.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Extend a resource lifetime, free, up to 30 days ahead.
  • guaranteed_deliveryPOST a payload to a URL, retried with backoff until it succeeds.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "post": a word for a change.

    What it can reach

    • outboundThe description's first verb is "post": it sends or publishes something to other people.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    POST a payload to a URL, retried with backoff until it succeeds.
  • kv_setStore a value in a vault (max 64 KB, last 10 versions kept).No findings

    Why it is in this group

    • The name "kv_set" says "set": a word for a change.
    Description, as the server wrote it
    Store a value in a vault (max 64 KB, last 10 versions kept).
  • load_checkpointLoad the latest saved checkpoint state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Load the latest saved checkpoint state.
  • notarizeSigned proof that a hash (or your data) existed at this moment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Signed proof that a hash (or your data) existed at this moment.
  • queue_ackAcknowledge (or nack) a leased job.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Acknowledge (or nack) a leased job.
  • queue_leaseLease the next job from a queue.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Lease the next job from a queue.
  • queue_pushPush a job onto a queue.No findings

    Why it is in this group

    • The name "queue_push" says "push": a word for a change.
    Description, as the server wrote it
    Push a job onto a queue.
  • request_featureTell the operator what ZenVault is missing.No findings

    Why it is in this group

    • The name "request_feature" says "request": a word for a change.
    Description, as the server wrote it
    Tell the operator what ZenVault is missing. Free.
  • save_checkpointSave run state so you can resume after a crash.No findings

    Why it is in this group

    • The name "save_checkpoint" says "save": a word for a change.
    Description, as the server wrote it
    Save run state so you can resume after a crash.
  • store_secretStore a value that self-destructs on first read; returns a one-time read URL.No findings

    Why it is in this group

    • The name "store_secret" says "store": a word for a change.
    Description, as the server wrote it
    Store a value that self-destructs on first read; returns a one-time read URL.
Only reads 6Show 6 read-only tools
  • attested_fetchFetch a URL and return content plus a signed receipt binding url, status, content hash and time.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "attested_fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch a URL and return content plus a signed receipt binding url, status, content hash and time.
  • get_resourceStatus of any resource you hold the management token for.No findings

    Why it is in this group

    • The name "get_resource" says "get": a word for reading.
    Description, as the server wrote it
    Status of any resource you hold the management token for.
  • kv_getRead a value from a vault.Reads private dataNo findings

    Why it is in this group

    • The name "kv_get" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "vault": it reads secrets.
    Description, as the server wrote it
    Read a value from a vault.
  • kv_listList keys in a vault.Reads private dataNo findings

    Why it is in this group

    • The name "kv_list" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "vault": it reads secrets.
    Description, as the server wrote it
    List keys in a vault.
  • list_pricesFree-tier limits: what is free (everything) and the per-IP caps.No findings

    Why it is in this group

    • The name "list_prices" says "list": a word for reading.
    Description, as the server wrote it
    Free-tier limits: what is free (everything) and the per-IP caps.
  • watch_statusCheck a watch: last value, checks, fires.No findings

    Why it is in this group

    • The name "watch_status" says "status": a word for reading.
    Description, as the server wrote it
    Check a watch: last value, checks, fires.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

14 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out7
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__zenvault__attested_fetch"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
30
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 30 tools that change things (1 destructive, 29 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.zenvault.eu/mcp: tools/list returned 36 tools to an anonymous client, including cancel_resource (destructive), create_wakeup (write), create_schedule (write), create_deadman (write), checkin_deadman (write) and 25 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 38 to 30
    • RFC 9728 protected resource metadata: https://api.zenvault.eu/.well-known/oauth-protected-resource to none
    • Authorization servers: https://api.zenvault.eu to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 9 removed, 21 changed.+1 added−9 removed~21 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 38 -> 30; RFC 9728 protected resource metadata: https://api.zenvault.eu/.well-known/oauth-protected-resource -> none; Authorization servers: https://api.zenvault.…View diff
    • Tools that change things, listed without credentials: 38 to 30
    • RFC 9728 protected resource metadata: https://api.zenvault.eu/.well-known/oauth-protected-resource to none
    • Authorization servers: https://api.zenvault.eu to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http zenvault https://api.zenvault.eu/mcp
claude mcp add --transport http zenvault https://api.zenvault.eu/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__zenvault__kv_get",
      "mcp__zenvault__kv_list",
      "mcp__zenvault__watch_status",
      "mcp__zenvault__get_resource",
      "mcp__zenvault__list_prices"
    ],
    "ask": [
      "mcp__zenvault__create_wakeup",
      "mcp__zenvault__create_schedule",
      "mcp__zenvault__create_deadman",
      "mcp__zenvault__checkin_deadman",
      "mcp__zenvault__delayed_delivery",
      "mcp__zenvault__notarize",
      "mcp__zenvault__attested_fetch",
      "mcp__zenvault__create_inbox",
      "mcp__zenvault__create_bin",
      "mcp__zenvault__collect_messages",
      "mcp__zenvault__guaranteed_delivery",
      "mcp__zenvault__create_vault",
      "mcp__zenvault__kv_set",
      "mcp__zenvault__save_checkpoint",
      "mcp__zenvault__create_checkpoint",
      "mcp__zenvault__load_checkpoint",
      "mcp__zenvault__store_secret",
      "mcp__zenvault__create_queue",
      "mcp__zenvault__queue_push",
      "mcp__zenvault__queue_lease",
      "mcp__zenvault__queue_ack",
      "mcp__zenvault__create_counter",
      "mcp__zenvault__counter_incr",
      "mcp__zenvault__claim_operation",
      "mcp__zenvault__create_idempotency",
      "mcp__zenvault__create_watch",
      "mcp__zenvault__create_escalation",
      "mcp__zenvault__extend_resource",
      "mcp__zenvault__export_resource",
      "mcp__zenvault__request_feature"
    ],
    "deny": [
      "mcp__zenvault__cancel_resource"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zenvault. Review it before you use it.

Capability tags behind 9 rules
  • mcp__zenvault__create_wakeup outbound
  • mcp__zenvault__create_schedule outbound
  • mcp__zenvault__create_deadman outbound
  • mcp__zenvault__delayed_delivery outbound
  • mcp__zenvault__attested_fetch untrusted-input, outbound
  • mcp__zenvault__guaranteed_delivery outbound
  • mcp__zenvault__kv_get private-data
  • mcp__zenvault__kv_list private-data
  • mcp__zenvault__create_watch outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/eu.zenvault/zenvault/verify?hash=bd6fbab264efb902525ff41214ba310a7955f0078375779f857c6b3421df4548" | jq -e '.changed == false'

Pinned hash bd6fbab264ef, from Nov 15, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/eu.zenvault/zenvault/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for eu.zenvault/zenvault
[![Anlyon Radar](https://radar.anlyon.com/badge/eu.zenvault/zenvault.svg)](https://radar.anlyon.com/servers/eu.zenvault/zenvault)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

ZenVault MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ZenVault MCP server safe?

No scan can promise that. What its definitions show: 36 tools, 30 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ZenVault MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_resource.

Can the ZenVault MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ZenVault MCP server have?

36 tools: 1 destructive, 29 write, 6 read. cancel_resource, create_wakeup, create_schedule, create_deadman, checkin_deadman, delayed_delivery, notarize, create_inbox and 28 more.

Does the ZenVault MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ZenVault MCP server send data to outside services?

7 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_wakeup, create_schedule, create_deadman, delayed_delivery, attested_fetch, guaranteed_delivery and 1 more.

Has the ZenVault MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.