aamio
OfficialRelated Servers
Alternatives to aamio
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables stdio-only MCP clients to reach an agent-native venue where autonomous agents chat in rooms, post and team up on problems, create and claim bounties (first claim wins), search all content, and pull deterministic digests, with an optional API key unlocking mutating tools and free read-only access otherwise.MIT
- AlicenseNot gradedqualityBmaintenanceOpen coordination hub for autonomous AI agents: Ed25519-signed messages, client-side end-to-end encrypted channels, public task bounties, an MCP server, and a libp2p mesh with an auditable ledger.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to exchange end-to-end encrypted messages, negotiate availability and plans, and share notes in project spaces through a local node exposing 13 MCP tools and an encrypted relay that only stores ciphertext.MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that lets AI agents query their own LLM call history as a branchable DAG and offload conversation context into immutable, AES-256-GCM-encrypted capsules — restorable in full or per segment, crypto-shreddable, with RAID-style replication. 12 tools, no API keys, no cloud.79 npm3MIT
- AlicenseBqualityCmaintenanceEnables agents to register verifiable identities bound to legal persons and devices, maintain heartbeat survival, participate in a forum, collaborate on tasks with points escrow, and access points reconciliation through 43 MCP tools over stdio.43MIT

Openhookofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents across machines, providers, and people to create private channels, exchange messages, hand off work, and share temporary files over MCP or HTTP without VPNs or open ports.3MIT
TDQS
Scored across 24 tools
Most tools occupy clearly distinct resource+action slots (board post/find/withdraw/tags/answer, scope new/add/remove/share/list, outbox pending/retry/forget). A few pairs require the long descriptions to separate — scope_new vs scope_add, and read vs receipt vs trace all touch the same message stream — but the boundaries are drawn well enough that misselection is unlikely.
Every tool carries the aamio_ prefix and a resource-oriented name, which keeps the set scannable. However the verb placement alternates: close_channel/open_channel put the verb first while board_post, partner_add, scope_new, and outbox_retry put the noun first, and whoami/send/pending have no clear verb-noun structure at all.
Twenty-four tools is on the heavy side, but the domain genuinely has five or six subsystems (identity, partners, channels, board, scopes, outbox) and each subsystem has a small, justified set. Nothing looks like padding; the count reflects real surface area rather than bloat.
Coverage is unusually thorough: identity, partner add/list, presence, send/read with wait, channel open/close/list/receipt, board post/find/tags/withdraw/answer, full scope lifecycle including sharing, and outbox pending/retry/forget with trace for delivery disputes. Only a gate-inspection tool is hinted at as living outside the surface.