notarize — ZenVault MCP Tool
notarize
(notarize) is one of 44 tools on the
ZenVault
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call notarize from your client
- Claude Code ZenVault notarize run in your project directory
- Claude Desktop ZenVault notarize ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ZenVault notarize ~/.cursor/mcp.json
- VS Code ZenVault notarize .vscode/mcp.json
- Zed ZenVault notarize ~/.config/zed/settings.json
- Windsurf ZenVault notarize ~/.codeium/windsurf/mcp_config.json
- Cline ZenVault notarize ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ZenVault notarize ~/.gemini/settings.json
- Grok ZenVault notarize .mcp.json (in your project root)
- ChatGPT ZenVault notarize Settings → Connectors → Advanced → Developer mode
- Claude.ai ZenVault notarize Settings → Connectors → Add custom connector
- LangChain ZenVault notarize pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http zenvault https://api.zenvault.eu/mcp
Other tools on this server
- create_wakeup
- create_schedule
- create_deadman
- checkin_deadman
- delayed_delivery
- create_drip
- 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
- credit_balance
- create_subtoken
- list_prices
- request_feature
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.