MCP.Market

WAKE Protocol MCP server

by Omodaka9375·io.github.Omodaka9375/wake·v2.2.2·3 stars
No reviews yet

A post-mortem succession protocol for AI agents. Black Box, handoff, time-locks.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

3 stars133 downloads/wk

Reviews

Write one

Nobody has reviewed WAKE Protocol yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

WAKE Protocol tools (23, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • configure_willwrite action

    Create or replace the WAKE Will. Generates auth tokens. SAVE the returned tokens.

  • contribute_knowledge

    Add a knowledge entry to the Black Box. Requires master token. Only in ACTIVE phase. Categories: finances, contacts, accounts, documents, decisions, commitments, medical, other.

  • delete_knowledgewrite action

    Delete a knowledge entry. Requires master token. Only in ACTIVE phase.

  • execute_terminal_statewrite action

    Execute terminal state (archive/distill/delete). Requires executor token. Only in EULOGY.

  • export_legal_will

    Generate a RUFADAA-compatible, human-readable legal export of the WAKE Will. Can be printed and attached to a traditional estate plan. Executor-only.

  • export_will

    Export the encrypted will state. Executor-only. Returns a portable blob.

  • get_access_tier

    Check access tier for a token holder.

  • get_audit_log

    Retrieve the audit log. Executor-only.

  • get_black_box

    Retrieve the Black Box. Content scoped by caller tier. Only in EULOGY/REST.

  • get_deletion_certificate

    Retrieve the deletion certificate for an owner whose data has been purged. Available after purge_owner_data is executed.

  • get_final_message

    Retrieve a final message. Requires valid token. Only in EULOGY/REST.

  • get_handoff_package

    Retrieve your own handoff package. Requires your beneficiary token. EULOGY/REST only. Returns structured JSON for agent ingestion.

  • get_status

    Get current WAKE protocol status. Optional token for details.

  • heartbeat

    Signal the owner is alive. Requires master token.

  • import_will

    Import a will from an exported encrypted blob. Replaces the current will for the ownerId.

  • initiate_handoff

    Initiate an agent-to-agent handoff for a beneficiary. Returns a structured JSON package. Executor-only. EULOGY/REST only.

  • list_backups

    List available backup snapshots. Executor-only.

  • list_knowledge

    List knowledge entries. Requires master token. Optional category filter.

  • purge_owner_data

    Permanently delete ALL data for an owner. Generates a deletion certificate first. Executor-only, REST phase only. IRREVERSIBLE.

  • restore_backup

    Restore a will from a backup snapshot. Executor-only.

  • trigger_vigil

    Manually force VIGIL phase. Requires master token.

  • update_willwrite action

    Update fields of the WAKE Will. Requires master token. Only in ACTIVE phase.

  • verify_death

    Confirm the death event. Requires verifier token. Only in VIGIL phase.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan54 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 151 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How WAKE Protocol compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
23
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
133
more than 69% of 12,191 servers with a package

What its tools let an agent do: 16 read · 1 create · 2 change · 2 delete · 2 run or deploy

Install WAKE Protocol in Claude Code, Cursor or VS Code

Runs npx -y wake-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add wake -- npx -y wake-mcp-server
Add to Cursor

What the publisher says

From the WAKE Protocol repository's README, as published. We do not edit it. Read it on GitHub

WAKE

Will-Aware Knowledge Execution — A post-mortem protocol for AI agents.

What happens to your agent when you're gone?

Structure

Quick Start

cd wake-mcp-server
pnpm install && pnpm run build
pnpm start        # stdio + dashboard on http://localhost:3000
pnpm test         # 69 tests

The Protocol

ACTIVE → VIGIL → EULOGY → REST

Your agent calls heartbeat on every interaction. When you stop responding, VIGIL triggers. A designated verifier confirms the death. EULOGY executes your succession plan — delivering final messages, activating tiered access to your Black Box, and initiating agent-to-agent handoffs. REST executes your terminal directive: archive, distill, or delete.

Everything is configurable: beneficiaries, redactions, time-locks, no-resurrection directives, jurisdiction, webhooks.

Documentation

  • MCP Server README — full tool reference, auth, deploy
  • SKILL.md — universal agent instructions

Author

Omodaka9375

License

Apache-2.0

Nothing above is checked by us. What we check is on the safety report.

WAKE Protocol: common questions

Is WAKE Protocol MCP server safe?
Mostly: it is graded B (82/100). Read the WAKE Protocol safety report
How do I install WAKE Protocol?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does WAKE Protocol need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is WAKE Protocol maintained?
The last commit was 189 days ago (2026-04-29). The latest release is v2.2.2.
How does WAKE Protocol compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 23 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from Omodaka9375 →