Slowtime MCP Server

What is Slowtime MCP Server?

A Model Context Protocol server for secure time-based operations with timing attack protection and timelock encryption. It integrates with Claude Desktop via MCP, providing interval management, timelock encryption, and timing attack prevention.

How to use Slowtime MCP Server?

Install by adding the server to your Claude Desktop config (claude_desktop_config.json) pointing to the built index.js. Then invoke tools such as start_interval, check_interval, pause_interval, resume_interval, encrypt (with interval ID), and list_vault_history with optional filters.

Key features of Slowtime MCP Server

• TimeFuzz – random delays and jittered timestamps against timing attacks
• TimeKeeper – create, pause, resume intervals with progress tracking
• TimeLock – encrypt data that decrypts only after an interval ends
• TimeVault – persistent DuckDB WASM storage with analytics
• drand network integration – distributed randomness for timelock security
• Constant-time comparisons – prevent side‑channel leakage

Use cases of Slowtime MCP Server

• Secure time‑release of sensitive messages or secrets
• Protect applications against timing side‑channel attacks
• Manage timed intervals (e.g., focus sessions) with MCP compatibility
• Audit and analyze encrypted timevaults with SQL‑like queries
• Prevent premature decryption of data until a defined interval expires

FAQ from Slowtime MCP Server

How does timelock encryption work?

Data is encrypted with a round number from the drand network. The decryption key is only released after the associated interval has ended, preventing early access.

What storage does Slowtime MCP Server use?

It uses DuckDB WASM for persistent storage of encrypted vaults, with a schema including id, encrypted_data, round_number, timestamps, and metadata.

How do I install Slowtime MCP Server?

Add a slowtime entry under mcpServers in your Claude Desktop config file, with "command": "node" and "args" pointing to the built build/index.js.

Does it require external dependencies?

Yes, it runs on Node.js and uses the drand network for randomness and DuckDB WASM for storage. No database server is needed.

Is there a license?

Yes, the project is licensed under the MIT License.