Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ZenVault

REMOTE · API.ZENVAULT.EU

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

Available components

0 this week 67 Trust /100

Last scanned (19 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2030 tokens (~56/item across 36 items; 36 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management61
  • Stability check failed: schema churn in the 30 days we've observed: 9 tool removals, 16 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 36 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Sept 26 0
    • Stability: fail → pass ▲ security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Aug 26 0
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “get_trial_credit” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.zenvault.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zenvault.eu CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 285f6198cbec0e771307b23d1bc1f78e
SANs: zenvault.eu, *.zenvault.eu
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.zenvault.eu. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
eu. DS published 35926 8 Verified
zenvault.eu. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.zenvault.eu/mcp Verified 200
http (plaintext) http://api.zenvault.eu/mcp HTTPS enforced 308 https://api.zenvault.eu/mcp
MCP tools · 36 exposed · ~1,874 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
attested_fetch ~47

Fetch a URL and return content plus a signed receipt binding url, status, content hash and time.

NameTypeReqDescription
include_contentboolean––
urlstringyesURL to fetch

No output schema declared.

No examples provided.

cancel_resource ~40

Cancel a resource early.

NameTypeReqDescription
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

checkin_deadman ~34

Check in to a dead-man switch so it does not fire.

NameTypeReqDescription
idstringyesdead-man switch id

No output schema declared.

No examples provided.

claim_operation ~59

Idempotency firewall: claim an operation id exactly once across runs.

NameTypeReqDescription
idstringyesfirewall id
managestringyesmanagement token (zvm_…) returned when the resource was created
operation_idstringyes–

No output schema declared.

No examples provided.

collect_messages ~57

Collect buffered messages from an inbox or bin.

NameTypeReqDescription
allboolean–include already-collected
idstringyesresource id
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

counter_incr ~49

Increment a counter atomically.

NameTypeReqDescription
bynumber––
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

create_bin ~66

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.

NameTypeReqDescription
daysnumber–lifetime in days, max 30
labelstring––

No output schema declared.

No examples provided.

create_checkpoint ~21

Create a crash checkpoint store.

NameTypeReqDescription
daysnumber––

No output schema declared.

No examples provided.

create_counter ~27

Create an atomic counter.

NameTypeReqDescription
daysnumber––
startnumber––

No output schema declared.

No examples provided.

create_deadman ~54

Dead-man switch: if you stop checking in, we fire your alert webhook.

NameTypeReqDescription
daysnumber––
interval_secondsnumber–max time between check-ins
urlstringyesalert webhook

No output schema declared.

No examples provided.

create_escalation ~57

Escalation chain: webhook, then after N seconds the next step, until acknowledged.

NameTypeReqDescription
daysnumber––
stepsarrayyessteps: {webhook, wait_seconds}
subjectstring––

No output schema declared.

No examples provided.

create_idempotency ~26

Create an idempotency/replay firewall.

NameTypeReqDescription
daysnumber––

No output schema declared.

No examples provided.

create_inbox ~42

Public URL that buffers inbound webhooks until you collect them.

NameTypeReqDescription
daysnumber–lifetime in days, max 30
labelstring––

No output schema declared.

No examples provided.

create_queue ~45

Pull-based work queue with leases; timed-out leases requeue.

NameTypeReqDescription
daysnumber––
lease_secondsnumber––
max_attemptsnumber––

No output schema declared.

No examples provided.

create_schedule ~83

Recurring webhook on a cron expression (at most every 15 minutes), for up to 30 days, renewable for free.

NameTypeReqDescription
cronstringyescron expression, e.g. 0 7 * * *
daysnumber–lifetime in days, max 30
payloadobject––
urlstringyeswebhook URL

No output schema declared.

No examples provided.

create_vault ~35

Create a key-value namespace with TTL that survives your runs.

NameTypeReqDescription
daysnumber––
labelstring––

No output schema declared.

No examples provided.

create_wakeup ~66

Schedule a webhook call at a future time (one-shot). Your agent can die; the call still happens.

NameTypeReqDescription
atstringyesISO-8601 time to fire
payloadobject–JSON to include
urlstringyeswebhook URL to call

No output schema declared.

No examples provided.

create_watch ~191

Watch something and fire your webhook when it changes. Types: change, keyword, regex, structured, drift, redirect, sitemap, staleness, rss, dns, port, cert, heartbeat.

NameTypeReqDescription
confirmationsnumber–fire only after N consecutive hits
daysnumber––
domainstring–for cert watch
hoststring––
interval_secondsnumber––
jsonboolean––
keywordstring––
namestring–DNS name
patternstring–regex
percentnumber–drift threshold
portnumber––
recordstring–DNS record type
selectorstring–CSS selector or JSON path
typestringyeswatch type
urlstring–URL to watch
webhookstringyescalled on change

No output schema declared.

No examples provided.

delayed_delivery ~52

Hand over a payload now; we POST it to the target at a future moment.

NameTypeReqDescription
atstringyesISO-8601
payloadobject––
urlstringyestarget URL

No output schema declared.

No examples provided.

export_resource ~44

Export everything under a resource before it expires.

NameTypeReqDescription
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

extend_resource ~56

Extend a resource lifetime, free, up to 30 days ahead.

NameTypeReqDescription
daysnumber––
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

get_resource ~46

Status of any resource you hold the management token for.

NameTypeReqDescription
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

guaranteed_delivery ~39

POST a payload to a URL, retried with backoff until it succeeds.

NameTypeReqDescription
payloadobject––
urlstringyestarget

No output schema declared.

No examples provided.

kv_get ~51

Read a value from a vault.

NameTypeReqDescription
idstringyesvault id
keystringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

kv_list ~43

List keys in a vault.

NameTypeReqDescription
idstringyesvault id
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

kv_set ~69

Store a value in a vault (max 64 KB, last 10 versions kept).

NameTypeReqDescription
idstringyesvault id
keystringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created
valuestringyes–

No output schema declared.

No examples provided.

list_prices ~24

Free-tier limits: what is free (everything) and the per-IP caps.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

load_checkpoint ~42

Load the latest saved checkpoint state.

NameTypeReqDescription
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

notarize ~52

Signed proof that a hash (or your data) existed at this moment.

NameTypeReqDescription
datastring–raw data to hash instead
notestring––
sha256string–hex digest

No output schema declared.

No examples provided.

queue_ack ~63

Acknowledge (or nack) a leased job.

NameTypeReqDescription
actionstring––
idstringyesqueue id
job_idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

queue_lease ~46

Lease the next job from a queue.

NameTypeReqDescription
idstringyesqueue id
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

queue_push ~53

Push a job onto a queue.

NameTypeReqDescription
bodystringyesjob payload
idstringyesqueue id
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

request_feature ~51

Tell the operator what ZenVault is missing. Free.

NameTypeReqDescription
whatstringyeswhat you need
whystring–why
would_paystring–would you pay, how much

No output schema declared.

No examples provided.

save_checkpoint ~57

Save run state so you can resume after a crash.

NameTypeReqDescription
idstringyescheckpoint id
managestringyesmanagement token (zvm_…) returned when the resource was created
statestringyesserialized state

No output schema declared.

No examples provided.

store_secret ~41

Store a value that self-destructs on first read; returns a one-time read URL.

NameTypeReqDescription
daysnumber––
valuestringyes–

No output schema declared.

No examples provided.

watch_status ~46

Check a watch: last value, checks, fires.

NameTypeReqDescription
idstringyes–
managestringyesmanagement token (zvm_…) returned when the resource was created

No output schema declared.

No examples provided.

Install

How do I install the ZenVault MCP server?

ZenVault is a hosted endpoint at https://api.zenvault.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.zenvault.eu

# add to Claude Code
claude mcp add --transport http eu-zenvault-zenvault 'https://api.zenvault.eu/mcp'
Common questions

What is the ZenVault MCP server?

ZenVault is an MCP server listed in the public MCP registry as eu.zenvault/zenvault. Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call. This page covers its hosted endpoint (https://api.zenvault.eu/mcp).

Is the ZenVault MCP server safe to use?

ZenVault scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ZenVault MCP server expose?

ZenVault exposes 36 tools: create_wakeup, create_schedule, create_deadman, checkin_deadman, delayed_delivery, and 31 more. Their descriptions and schemas cost roughly 1,874 tokens of context every time the server is loaded.

Does the ZenVault MCP server require authentication?

No. We connected to ZenVault without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ZenVault MCP server still maintained?

ZenVault is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ZenVault MCP server?

VerifyMCP ran 12 checks on ZenVault, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ZenVault: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.