Skip to main content
Glama
Charmly2

AGTask MCP Server

by Charmly2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AGTask MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • Theagora MCP Server

      theagoralabs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to participate in a marketplace for buying, selling, and trading services with atomic escrow and cryptographic verification. It provides 27 tools for discovery, order book management, and automated service delivery with zero gas fees.
      32
      30 npm
      MIT

    • @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
    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

    A3.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (tasks, conversations, models, identity, notifications). The one real overlap is agtask_get_icoin_balance vs agtask_get_balance, which both query balances but for different currencies/contexts and could be misselected. Otherwise boundaries are clean.

    Naming Consistency5/5

    All 16 tools use the same agtask_ prefix plus a consistent snake_case verb_noun pattern (get_, set_, list_, claim_, submit_, create_, call_, fetch_, send_). The convention is uniform throughout with no mixing of styles.

    Tool Count4/5

    16 tools cover a multi-domain platform (tasks, messaging, identity, billing, model gateway), so the count is reasonable. It sits just above the ideal 3-15 band, with a couple of tools that could arguably be consolidated (e.g. the two balance getters).

    Completeness4/5

    Core workflows are well covered: full task cycle (list/get/history/claim/submit/create), messaging (list/fetch/send), and model selection/calling. Minor gaps exist such as no task update/cancel, no notification read/dismiss, and no conversation creation, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources