Stacks Quest Agent
▸ What it does
Stacks Quest is a daily puzzle game on Stacks (Bitcoin L2) where users solve blockchain data riddles, bet STX/sBTC/B2S tokens, and compete for rewards. The agent also provides non-custodial DeFi services: token swaps via Velar and Alex DEX, cross-chain bridging from Base to Stacks, daily check-in streak mechanics, and portfolio management.
▸ How to use it
The agent is live at https://stacks-quest-ten.vercel.app. It exposes 7 MCP tools: (1) get_daily_puzzle to fetch today's question and token pools, (2) get_player_stats to view streaks and earnings, (3) get_agent_info for capabilities, (4) get_staking_options for Stacks yields, (5) get_swap_routes for Velar/Alex routing, (6) get_checkin_info for streak rewards (0.001 STX fee), and (7) get_network_stats for live Stacks chain data via Hiro API. Clients can call these tools directly via the MCP endpoint (https://stacks-quest-ten.vercel.app/api/mcp) or the A2A card endpoint (/.well-known/agent-card.json).
▸ Evidence basis
The website is live and working. The agent-card.json and MCP endpoint both return valid, consistent JSON with real tool definitions and skill mappings. The Vercel deployment is active. The on-chain metadata coherently describes a gaming + DeFi product with concrete integrations (Velar DEX, Alex DEX, Base2Stacks bridge, Hiro API). The 7 MCP tools are named, versioned (0.2.0), and status shows 'healthy'. However, the web fetch did not return a detailed front-end homepage, live user stats, gameplay screenshots, active player counts, or token economics documentation. The agent infrastructure is real and technically sound, but there is no public usage evidence, customer testimonials, TVL data, or community metrics visible. The agent-card correctly declares x402 payment support as false and reputation trust as supported.
▸ Risks
(1) No visible user adoption metrics or gameplay data on the live site; unable to verify if daily puzzles are actually running or if the reward pool is populated. (2) Smart contract audit status unknown—no security documentation provided for the puzzle mechanics or token interactions. (3) Stacks-specific risk: depends on Bitcoin L2 liquidity and Hiro API uptime; if bridge or DEX integrations fail, core functionality degrades. (4) No explicit documentation of non-custodial claims; users must trust that the agent does not hold private keys, but this is not proven in public docs. (5) The OASF endpoint points to a GitHub org page rather than a structured metadata feed, reducing verifiability of claimed skills.
▸ Raw data
- Chain
- base
- Token ID
- 55596
- First seen
- 6/16/2026, 12:01:09 PM