mcpdirectory.dev
9,129 servers · updated 23 Sept

Hydrate Dehydrate MCP server

official from Slidingbox Active last commit 18 d
{
  "mcpServers": {
    "hydrate-dehydrate": {
      "command": "npx",
      "args": [
        "-y",
        "@slidingbox/hydrate-dehydrate-mcp@latest"
      ],
      "env": {
        "SLIDINGBOX_API_KEY": "<slidingbox_api_key>",
        "SLIDINGBOX_PRIVATE_KEY": "<slidingbox_private_key>",
        "SLIDINGBOX_URL": "https://..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @slidingbox/hydrate-dehydrate-mcpversion 0.3.0

What it does

An MCP server for one-time encrypted secret handoff between agents, machines, or people. It encrypts secrets locally using AES-256-GCM, stores only ciphertext on the server, and destroys the secret after the first successful retrieval. Intended for developers who need to pass credentials or secrets through a channel without leaving a persistent copy.

  • Pass an API key or credential from one agent to another when they share no common secret store or account.
  • Send a secret through a chat or log channel so the token becomes inert after it is read once.
  • Confirm a one-time handoff occurred, because a replayed token visibly fails instead of silently serving the secret again.

Tools this server exposes

ToolDoes
store_secretEncrypts a secret locally and uploads the ciphertext to Slidingbox, returning a token that encodes both a server pointer and the encryption key.
retrieve_secretDecrypts and returns the secret associated with a token exactly once, then destroys it on the server so subsequent reads return nothing.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.