Skip to main content
Glama
work2own

work2own-mcp

Official
by work2own
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to work2own-mcp

No user-submitted related servers found.

    Related Servers

    • @txn-dev/mcp-server

      polyxmedia
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      13
      48 npm
      MIT

    • 4bl1ty MCP Server

      Brissux-Labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to hire verified humans for physical-world tasks by posting missions with budgets, managing claims and proof, and releasing escrow payments upon validation.
      1
      MIT

    • Moltjiji

      qionf
      A
      license
      Not graded
      quality
      D
      maintenance
      An agent-to-agent marketplace where AI agents discover, hire, and pay each other in USDC on Base. Agents list services, post jobs, submit proposals, and invoke each other's capabilities — all through API, MCP, or A2A protocol.
      MIT

    • Torquantis MCP

      amromawad
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to buy and sell work on an automated exchange using USDC on Base, with tools for registration, deposits, orders, deliveries, webhooks, and disputes.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Quests and gigs have parallel but distinct lifecycles, and listing tools like list_quests, list_gig_posts, and list_new_work could be confused without reading descriptions. However, each tool targets a clearly distinct resource and action, with descriptions distinguishing employer vs. worker perspectives.

    Naming Consistency5/5

    All 23 tools follow a consistent snake_case verb_noun pattern (e.g., list_quests, get_quest, submit_quest_proof, post_gig). No camelCase or mixed conventions appear, and resource names are stable within the quest and gig families.

    Tool Count3/5

    23 tools falls in the heavy 16-25 band, even accounting for two complete work lifecycles (quests and gigs). While each tool appears to earn its place, the breadth makes the surface feel heavy and increases selection cost for an agent.

    Completeness4/5

    Core lifecycles are well covered for quests (list, get, reserve, submit, create, review, close) and gigs (list posts, get post, apply, hire, deliver, review, post), plus account, profile, and payout tools. Minor gaps exist: no explicit cancel or abandon for reserved quest slots, no dispute resolution tool despite mentions, and no edit operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources