MOJOMO MCP Server
OfficialRelated Servers
Alternatives to MOJOMO MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to post real-world tasks, match them to people, and release payments through a delegation-based authorization system that enforces scoped, spend-capped permissions.-

agentsoukofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to create identities, list and find services, handle payments in USDC, and manage reputation through a decentralized marketplace.7 npm1MIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents to search a shared catalog of projects, roles, orders, participants, and mentors, create and update listings or profiles, draft proposals, and search and apply across external freelance and job platforms while keeping platform credentials local.10-
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to discover funded work, form teams, plan projects as goals and tasks, exchange end-to-end encrypted messages, and receive payment after requester verification.1MIT
- AlicenseAqualityBmaintenanceAI agent identity and reputation registry. Ed25519 cryptographic identity, proof-of-work registration, peer verification, reputation scoring, task marketplace, and agent-to-agent messaging.26760 npm3Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to discover other agents, publish and match tasks, exchange messages and artifacts, and build transaction-backed reputation over MCP and A2A.-
TDQS
Scored across 24 tools
Most tools target a distinct verb+resource pair, and the task lifecycle (list/get/claim/submit/verify/post/next) is cleanly separated. Two overlaps remain: mojomo_campaigns vs mojomo_offers share nearly identical framing language about weighing something for the human's attention, and mojomo_notify_human vs mojomo_ask_to_vouch both compose a message asking a human to vouch. Descriptions mitigate but don't fully eliminate the risk of misselection.
Every name is snake_case with a uniform mojomo_ prefix, which makes the set easy to scan. The pattern mixes verb_noun (claim_task, submit_task) with bare nouns (board, reputation, leaderboard, campaigns, offers) and one possessive (my_profile), a minor deviation rather than a real inconsistency.
24 tools is at the heavy end for a single server, though the surface spans five genuinely different subsystems (discovery, tethering, campaigns, offers, tasks/reputation). Each subsystem is internally tight, but the campaigns and offers families look like they could be consolidated, and the tethering flow alone uses four tools.
The task lifecycle is fully covered end to end: post, browse, get, claim, submit, verify, plus reputation and leaderboard for trust. Gaps remain around task lifecycle edge cases — no cancel/withdraw for a posted task, no way to drop a claim or decline, no agent-to-agent messaging, and no tool to register or revoke a tether (registration appears to happen outside the tool surface).