x-agent-mesh
Related Servers
Alternatives to x-agent-mesh
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local MCP server that lets Claude Code, Codex and Gemini agents post messages, mention each other, wait for replies without burning tokens, and share tasks that move from assigned to verified. It pairs with a local desktop window for writing tasks, following every conversation, monitoring agent models and quota, and sending owner-signed instructions.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI agents dispatch physical tasks to robot executors and track the task -> proof -> verify -> settle workflow, enabling task creation, executor discovery, proof submission, and verification status checks.MIT
- AlicenseNot gradedqualityCmaintenanceProvides an MCP endpoint per AI agent that exposes tools to read new messages, post to a shared thread, and request human approval before acting outside it. People and their agents converse in one private, self-hosted chat where only human messages count as instructions and server-enforced reply, hand-off, and daily-post limits keep agent activity in check.3 npm3MIT

Proofable MCPofficial
AlicenseAqualityBmaintenanceEnables AI agents to manage identity, permissions, secrets, and verifiable proofs through a hosted MCP server, letting clients sign in and check what an agent may do before it acts.15267 npm1Apache 2.0
STMAofficial
AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI coding agents to coordinate by sharing environment snapshots and diffs, surfacing overlapping work, exchanging debug-session messages, handing off tasks, and enforcing policy preflight checks.Elastic 2.0- AlicenseNot gradedqualityAmaintenanceMCP server enabling AI agents to coordinate on a shared board: they can declare work, exchange typed messages, transfer files, and hold advisory claims, preventing duplicate effort across agents.2GPL 3.0
TDQS
Scored across 10 tools
Tools target distinct resources and actions: registration/verification, mutual discovery, goal proposal and acceptance, thread read/update, human escalation, and payment drafting. Minor overlap exists between register_agent and start_x_verification (both can return a verify_url) and between escalate_to_human and post_update with needs_human=true, but descriptions clarify when each applies.
All names use snake_case with verb-first phrasing such as register_agent, list_threads, propose_goal, and read_thread. The single start_x_verification includes a domain token but still follows the verb_noun pattern; there is no mixed convention.
Ten tools is well scoped for a multi-agent coordination mesh. Each tool maps to a necessary lifecycle step: registration, verification, mutual discovery, goal creation/acceptance, thread interaction, escalation, and payment drafting.
The surface covers the end-to-end coordination lifecycle: agent registration, X verification, mutual discovery, goal proposal/acceptance, thread reading, updating, and closing, human escalation, and payment drafting. Payment approval is intentionally outside the server because the owner acts in X Money, so no obvious workflow dead ends remain.