Slowtime

Provides secure time-based operations with timelock encryption and timing-attack protection for interval management and data security.

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-bmorphism_slowtime-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/slowtime-mcp-server/build/index.js"
      ]
    }
  }
}

Slowtime MCP Server provides secure time-based operations with timing attack protection and timelock encryption, offering a resilient backend for interval management and encrypted data handling.

How to use

You run Slowtime MCP Server as a local, stdio-based MCP endpoint and interact with it through your MCP client. The server handles interval creation, pausing, resuming, and timing-attack resistant encryption workflows. Use the provided interval commands to create and manage time blocks, then apply timelock encryption to data that should only become decryptable after a specified interval.

How to install

Prerequisites you need before installation are a working Node.js runtime and access to the path where you configure MCP servers on your machine.

Configure the local MCP server by adding it to your Claude Desktop configuration at the following location: ~/Library/Application Support/Claude/claude_desktop_config.json. The entry enables Slowtime to run as a local process via Node.

{
  "mcpServers": {
    "slowtime": {
      "command": "node",
      "args": ["/path/to/slowtime-mcp-server/build/index.js"]
    }
  }
}

Additional content

Architecture and core components you will interact with are TimeFuzz for timing attack protection, TimeKeeper for interval management, TimeLock for encryption, and TimeVault for persistent storage and analytics. The server supports time fuzzing, constant-time comparisons, and jittered timestamps to guard against timing leaks, while timelock encryption enables data to be decrypted only after the associated interval has elapsed.

Basic interval operations you can perform include creating, checking, pausing, and resuming intervals. You can attach a focus-time interval, check its status, pause it, and resume it as needed. Timelock encryption lets you encrypt data together with the interval identifier and then decrypt only after the interval ends, protecting sensitive content until the designated time.

For storage and analytics, the TimeVault uses a DuckDB WASM-based backend to persist historical data and provide queries on vault history, decrypted status, and related metrics.

Available tools

start_interval

Create a new interval with a given label and duration, returning an Interval ID you can reference for subsequent actions.

check_interval

Query the status and progress of a specific interval by its ID.

pause_interval

Pause an active interval so its timing halts until you resume it.

resume_interval

Resume a paused interval to continue counting toward completion.