MCP Server for AI Agents

Inheribase provides a Model Context Protocol (MCP) server that enables AI agents to interact with your vault securely.

Installation

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

Available Tools

store_asset

Store any file in your encrypted vault.

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

Parameters:

filename (required): Name of the file
data (required): File content as base64 or UTF-8 text
contentType (optional): MIME type
metadata (optional): Custom metadata
vaultId (optional): Target vault ID

check_status

Check your vault status and release timing.

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.

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"
      }
    }
  }
}

Security

All data is encrypted client-side with AES-256-GCM
API keys have scoped permissions
Rate limiting protects against abuse
See our Security Architecture for details

Migration from v1.x

Tool names were updated in v2.0.0 for clarity:

Old Name	New Name
`store_secret`	`store_asset`
`check_dead_man_switch`	`check_status`
`log_life_proof`	`check_in`

The old names work as aliases until v3.0.0.

MCP Server

On this page