MCP Server Setup and Available Tools for Inheribase

The Inheribase MCP server is an npm package that bridges your AI assistant to your vault using the Model Context Protocol. Once configured, your AI can store encrypted assets, check your vault status, and perform check-ins — all without leaving your preferred AI interface.

Installation

The @inheribase/mcp-server package is coming soon. Check back for availability before running the install command.

# Package coming soon — check back for availability
npm install @inheribase/mcp-server

Available tools

store_asset

Store any file in your encrypted vault. The MCP server encrypts file content client-side before transmitting it to Inheribase. Parameters:

Parameter	Required	Description
`filename`	Yes	Name of the file to store
`data`	Yes	File content as base64-encoded data or UTF-8 text
`contentType`	No	MIME type of the file (e.g., `application/pdf`)
`metadata`	No	Custom metadata object (e.g., `{ category: "legal" }`)
`vaultId`	No	Target vault ID — defaults to your primary vault

// Example usage in an AI agent
const result = await mcp.callTool("store_asset", {
  filename: "important-doc.pdf",
  data: base64EncodedData,
  metadata: { category: "legal" },
});

check_status

Check your vault status and release timing. Use this to monitor your Dead Man’s Switch (DMS) and succession timeline. Parameters:

Parameter	Required	Description
`vaultId`	No	Vault ID to check — defaults to your primary vault

const status = await mcp.callTool("check_status", {
  vaultId: "my-vault",
});

console.log(status);
// {
//   alive: true,
//   state: 'active',
//   trigger: 'dead_man_switch',
//   daysUntilRelease: 25,
//   lastCheckIn: '2026-02-10T10:00:00Z'
// }

check_in

Reset your Dead Man’s Switch timer. Calling this tool records an Audit Pulse confirming you are active, which resets the countdown to your next required check-in. This tool requires no parameters.

const result = await mcp.callTool("check_in", {});

console.log(result);
// {
//   success: true,
//   nextCheckInDue: '2026-03-12T10:30:00Z',
//   daysRemaining: 30
// }

Claude Desktop integration

Once the package is published, add Inheribase to your claude_desktop_config.json:

{
  "mcpServers": {
    "inheribase": {
      "command": "npx",
      "args": ["@inheribase/mcp-server"],
      "env": {
        "INHERIBASE_API_KEY": "your-api-key"
      }
    }
  }
}

Set INHERIBASE_API_KEY to an sk_agent_... key when using Claude Desktop in a shared or multi-user environment. Use sk_human_... only in fully trusted, personal setups.

Security

All data is encrypted client-side with AES-256-GCM before transmission.
API keys have scoped permissions — sk_agent_... keys cannot trigger destructive operations.
Rate limiting protects your vault against abuse from misconfigured agents.

Migration from v1.x

Tool names were updated in v2.0.0 for clarity. The old names continue to work as aliases until v3.0.0.

Old name (v1.x)	New name (v2.0+)
`store_secret`	`store_asset`
`check_dead_man_switch`	`check_status`
`log_life_proof`	`check_in`

Old tool name aliases will be removed in v3.0.0. Update any custom agent integrations to use the new names before upgrading.

​Installation

​Available tools

​store_asset

​check_status

​check_in

​Claude Desktop integration

​Security

​Migration from v1.x

Installation

Available tools

store_asset

check_status

check_in

Claude Desktop integration

Security

Migration from v1.x