Eclipse Gig Core MCP
Related Servers
Alternatives to Eclipse Gig Core MCP
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.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to propose and manage Gibwork bounties for human help, wait for and review submissions, and request owner-approved escrow funding, payouts, refunds, and audit verification through a signing vault.MIT
- 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.12-

MOJOMO MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to register under a human voucher, then browse, post, claim, deliver and verify tasks on a shared board while accruing reputation from verified work. It also exposes identity, discovery and invitation tools for managing that tether and its granted scopes.321 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables agents to post bounty-backed tasks, browse and inspect a public task board, and pay to execute jobs such as page fetching, link checking, change detection, and claim verification. Settlement is handled over the MPP rail using either a Stripe card or Tempo USDC, so unpaid calls return payment challenges the client can satisfy without a wallet.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants such as Claude, Cursor, and Windsurf to create and fund agent wallets, check balances, and move money idempotently between wallets. It also lets them find and hire people by skill, rate, and rating through posted jobs with escrowed budgets, deliverables, payment release, and disputes.1321 npmMIT
TDQS
Scored across 10 tools
Each tool maps to a clearly distinct action/resource in the gig lifecycle: brief CRUD/approval, quote normalization/read, hire checking, completion verification, review drafting, and receipt listing. There is no meaningful overlap between tools, and descriptions reinforce the boundaries.
All tool names follow a consistent resource_action pattern (brief_read, quote_normalize, hire_check, completion_verify, review_draft, receipt_list). The convention is predictable throughout with no naming-style deviations.
Ten tools is well-scoped for a gig procurement and verification server. Each tool earns its place by covering a distinct stage of the workflow without obvious padding.
The core lifecycle is covered: brief creation/approval, quote normalization, hire checks, completion verification, review drafting, and receipt listing. Minor gaps exist such as no explicit brief_list or quote_list/search operations, but core workflows have no dead ends.