Slowtime MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Slowtime MCP Server?

Slowtime MCP Server is a Model Context Protocol server designed for secure time-based operations, featuring timing attack protection and timelock encryption.

How to use Slowtime MCP Server?

To use the Slowtime MCP Server, integrate it into your Claude Desktop configuration and utilize basic interval commands for managing time intervals and encrypting data.

Key features of Slowtime MCP Server?

  • Timing attack prevention through random delays and constant-time comparisons.
  • Timelock encryption for secure data handling.
  • Interval management for creating, pausing, and resuming time intervals.
  • Analytics and statistics for tracking encrypted data.

Use cases of Slowtime MCP Server?

  1. Securely managing focus intervals for productivity.
  2. Encrypting sensitive data with time-based access controls.
  3. Analyzing historical data for encrypted time vaults.

FAQ from Slowtime MCP Server?

  • What is the purpose of the Slowtime MCP Server?

It provides secure time-based operations with features like timing attack protection and timelock encryption.

  • How do I install the Slowtime MCP Server?

Add the server configuration to your Claude Desktop config file as specified in the installation section.

  • Can I use it for any type of data?

Yes, it is designed to handle various types of sensitive data securely.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago