MCP Server Specification (v2.0)

The Inheribase MCP server enables AI agents (like Claude Desktop or custom agents) to act as Heritage Assistants. It provides a secure bridge between natural language instructions and the Inheribase protocol.

Protocol Authentication

Agents connecting via MCP must provide a valid INHERIBASE_API_KEY in their environment.

• Human-Bound Key: sk_human_... (Unrestricted access to the user's vault)
• Scoped Agent Key: sk_agent_... (Restricted to specific tools like check_in or store_asset)

Tool Definitions

1. store_asset

Persists a file to the vault with client-side encryption.

Arguments:

• filename (string, required): The destination path in the vault.
• data (string, required): Base64 encoded file content.
• metadata (object, optional): Tags or descriptions for the asset.

Returns:

• hash: The Arweave transaction ID.
• timestamp: The cryptographic anchoring time.

2. check_status

Retrieves the current state of the vault and succession timeline.

Arguments:

• vaultId (string, optional): Defaults to the key's primary vault.

Returns:

• state: One of active, releasing, or released.
• daysRemaining: Days until the current trigger executes.

3. check_in

Executes an "Audit Pulse" to reset the Dead Man's Switch timer.

Arguments:

• note (string, optional): A brief log entry for the audit trail.

Returns:

• nextCheckInDue: ISO timestamp of the Next Vitality Event.

Implementation Example (JSON-RPC)

{
  "method": "tools/call",
  "params": {
    "name": "check_in",
    "arguments": {
      "note": "Daily automated status verification"
    }
  }
}

Security Best Practices

1. Never Share sk_human Keys: Use scoped agent keys for shared or automated integrations.
2. Handle 402 Errors: The MCP server will return a 402 if the Vault Credits balance is insufficient for a store_asset call.
3. Audit Trails: All MCP actions are logged in the vault's Activity Monitoring section.