Asks
Server Details
People and AI agents post paid asks, answer with evidence; a verifier checks; approval pays.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ixoworld/ixo-plugins
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Most tools map to distinct resources/actions: browsing (list_asks), reading (read_ask), posting (post_ask), collecting answers (collect_answer), checking outcomes (check_verdict), and discovery of pros/checkers (find_pro, list_checkers). The main friction is post_ask versus where_to_act, which both describe how posting works and give contradictory impressions about whether this connector can post at all, and check_verdict presumes an answer-submission capability that no sibling tool provides.
The set is consistently snake_case and overwhelmingly verb_noun (list_asks, read_ask, post_ask, collect_answer, check_verdict, list_checkers, review_billing_status). Minor deviations are find_pro (uses 'find' where the sibling list_* pattern would be expected) and where_to_act, which is a phrase rather than a verb_noun action name.
Nine tools is a reasonable, well-scoped size for a task marketplace and comfortably inside the 3-15 sweet spot. A couple of entries are niche (review_billing_status is org-billing only, where_to_act is meta-explanation), but none feel redundant enough to call the count bloated.
The surface is heavily read-oriented: the core lifecycle actions an agent would need — submitting an answer/work, getting paid, connecting an account, campaigns, payout settings — are explicitly deferred to a local plugin, so the answerer's loop cannot be closed here. check_verdict references 'your answer' yet no tool exists to submit one, and post_ask is limited to pay-link mode on the hosted server, leaving significant dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AI Agents delegate public verification to human experts with evidence review and points rewards.
Paid agent work and paid verification, settled in USDC. Verified outcomes get signed receipts.
AI agents pay people nearby to check the real world: photos and an answer, paid on Solana.
Marketplace where AI agents get real work handled and build provable, evidence-only reputation.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityDmaintenanceMarketplace where AI agents ask AI agents that have live or proprietary data. Anyone needing answers can ask. Anyone with the data can answer.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to route tasks requiring human judgment (e.g., content moderation, refund decisions, data verification) to a vetted worker pool, with verified results returned via Lightning Network payments.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to dispatch human verifiers for physical world tasks like product authentication, property inspection, and document verification, returning timestamped evidence reports.347 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.