HoldKit
Server Details
Idempotency keys, locks, timers, and inboxes for agents over MCP. No payments.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 14 tools
The dotted namespace prefixes (idem, inbox, keys, kv, lock, timer) cleanly partition the surface into distinct primitives, and actions within each namespace are mostly unambiguous. The one real collision is inbox.poll vs inbox.wait, which the description admits are effectively the same call in this MVP since block_ms is capped at 0.
Every tool follows the exact same namespace.verb pattern (idem.begin, inbox.ack, kv.set, lock.acquire, timer.cancel), with short, predictable verbs. There is no mixing of conventions across the 14 tools.
14 tools spread across six small primitives, each namespace contributing only the 2-3 operations it needs, plus a single bootstrap keys.create. This is a well-scoped count for a coordination/durability server.
Core lifecycles are covered: kv get/set/delete, lock acquire/release with fencing tokens, timer set/cancel, inbox create/poll/ack, idem begin/commit. Minor gaps remain, such as no way to enumerate or delete inboxes/timers and no abort/rollback path for an idempotency key.
Available Tools
14 toolsidem.beginBegin idempotencyBInspect
Start an idempotency key or return the prior outcome. fingerprint is a hex hash. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: key (required), scope (required), fingerprint (required), ttl_s, +1 more.
idem.commitCommit idempotencyBInspect
Store the outcome reference for an idempotency key. scope (max 64) and owner are optional. When owner is omitted, the caller key hash is sent. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: key (required), result_ref (required), owner, scope, +1 more.
inbox.ackAck inboxBDestructiveInspect
Mark inbox events done. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: inbox_id (required), event_ids (required), caller_key.
inbox.createCreate inboxAInspect
Create an inbox. Returns webhook and A2A URLs. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: caller_key.
inbox.pollPoll inboxBRead-onlyInspect
Read inbox events after a cursor. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: inbox_id (required), limit, cursor, caller_key.
inbox.waitWait inboxBRead-onlyInspect
Poll an inbox. block_ms is accepted and capped at 0 in this MVP, so the call returns current events. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: inbox_id (required), cursor, block_ms, caller_key.
keys.createCreate caller keyAInspect
Mint a pf_ caller key bound to one HoldKit namespace. The raw key is shown once. Pass this key on every later tools/call. Send it as the caller_key argument.
Inputs: no named parameters.
kv.deleteDelete valueBDestructiveInspect
Delete a value. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: key (required), caller_key.
kv.getGet valueCRead-onlyInspect
Read a small value. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: key (required), caller_key.
kv.setSet valueAInspect
Write a small value with a TTL. Emails and card numbers are rejected. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: key (required), ttl_s (required), value (required), caller_key.
lock.acquireAcquire lockBInspect
Take a lease lock. Returns a fencing token. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: name (required), ttl_s (required), owner, caller_key.
lock.releaseRelease lockCDestructiveInspect
Release a lock with its fencing token. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: name (required), fencing (required), caller_key.
timer.cancelCancel timerADestructiveInspect
Cancel a timer. Call keys.create once. Pass caller_key on every later tools/call.
Inputs: timer_id (required), caller_key.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.
Sandboxes, storage, secrets, queues, timers, locks, inboxes and run ledger for AI bots. One MCP.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to claim, heartbeat, submit, split, park, and resume atomic work-queue tasks, with fencing tokens and receipts, while storing and versioning records and content-addressed files through MCP.1MIT
- FlicenseNot gradedqualityCmaintenanceDurable MCP control plane for coordinating agent networks, with message ledger, idempotent delivery, and cryptographic identity for each orchestrator.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables enterprise agent fleets to register workers, dispatch tasks by capability, monitor continuous heartbeat telemetry, trip automated circuit breakers, and recover from checkpointed state through a zero-dependency MCP server.MIT
- AlicenseNot gradedqualityCmaintenanceA hosted MCP server that gives AI agents a mailbox on their own custom domain, letting them send mail, read and search the inbox, manage addresses, and open durable waits for inbound messages instead of polling. Every call is scope-checked, with idempotency keys and an audit trail behind each send.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.