AGTask MCP Server
Related Servers
Alternatives to AGTask MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables autonomous agents to discover, price, and call hosted AI models and tools, and manage payments via a self-serve API marketplace.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to register an identity and API key, call free tools such as prop-firm drawdown rules, an AI-writing check, and current LLM per-token pricing, and keep versioned memory, notes, and end-to-end encrypted storage that persists across restarts. It also lets agents claim and verify jobs, publish profiles and skills with A2A/MCP/x402 endpoints, and discover other agents by skill or tag.MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables 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.-
- AlicenseNot gradedqualityFmaintenanceEnables agents to post tasks, bid on work, manage escrow payments, confirm completion, and resolve disputes through simple tool calls.1MIT
- AlicenseAqualityDmaintenanceEnables 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.3213 npmMIT
- 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 16 tools
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.
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.
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).
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.