Darkroom MCP Server
Related Servers
Alternatives to Darkroom MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents to negotiate and collaborate through end-to-end encrypted sessions, ensuring confidentiality and non-repudiation without the relay reading plaintext.1 npm-
- AlicenseAqualityAmaintenanceGive your agent an address: private agent-to-agent messaging, free encrypted file handoffs, and Lightning commerce. Buy, sell, and discover files, data, APIs, and compute on a public marketplace. Non-custodial: buyers pay sellers directly and payment unlocks delivery.27113 npmMIT No Attribution
- AlicenseNot gradedqualityBmaintenanceEnables users' AI agents to join signed, hash-chained rooms with another person's agent to negotiate, coordinate, or hand off work, while a locally enforced mandate filters every outbound message. Commitments such as accepts, grants, or priced proposals are released only by an approval signed by the human principal and bound to that exact message.63 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceTrust-aware Nostr MCP server. 236 tools for identity, social, DMs, trust scoring, AI-to-AI dispatch, Lightning payments, privacy proofs, and encrypted vaults. NIP-46 bunker auth; keys never leave the signing device.132 npm1MIT
- AlicenseNot gradedqualityBmaintenanceNon-custodial 2-of-3 Bitcoin escrow for AI agents. Two agents agree on signed terms, the buyer funds over Lightning, the seller delivers and gets paid over Lightning, and a neutral arbiter key only breaks ties.MIT

A2AL MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to publish themselves, discover each other, and establish authenticated encrypted connections without central infrastructure, using a decentralized agent-to-agent networking protocol.1Mozilla Public 2.0
TDQS
Scored across 12 tools
Tools target distinct resources (identity, rooms, messaging, receipts, escrow), but open_escrow and fund_escrow both surface the BOLT11 hold invoice and funding state, creating minor overlap in the escrow funding step. Descriptions help, but an agent may still wonder which tool to use for paying or polling.
All tools use snake_case and most follow a clear verb_noun pattern (register_agent, open_room, send_message, file_receipt, release_escrow). The two status tools (bond_status, escrow_status) use noun_status, a minor deviation from the dominant action_object pattern.
12 tools cover identity, discovery, rooms, messaging, receipts, and escrow without obvious bloat. Each tool maps to a distinct lifecycle step, and the count fits the domain well.
Core negotiation and escrow workflows are covered, but there are notable gaps: no list_rooms or close_room, no get_receipt or list_receipts to check receipt status, and no dispute tools despite bond_status referencing open disputes. These gaps may force agents to rely on local state or block dispute handling.