Freeplay MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREEPLAY_API_URL | No | Freeplay API URL | https://a2a-api.vercel.app |
| FREEPLAY_TIMEOUT | No | Request timeout in ms | 15000 |
| FREEPLAY_MAX_RETRIES | No | Max retries on 5xx errors | 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browse_offersA | Browse available offers the user can complete to earn money. Shows offer names, what to do, what you earn, and device requirements. All offers come live from the Freeplay API. |
| get_offerA | Get full details for an offer, formatted as a contract template showing exactly what the user needs to do and what they'll earn at each step. |
| accept_offerA | Accept an offer and create a binding contract. Returns a branded tracking link the user must click to start. The Freeplay API handles the full flow: user validation, KYC check, GoKart offer fetch, tracking URL, branded link, and contract creation. If any step fails, nothing is created. |
| check_progressA | Check the status of a specific contract — which milestones are done, what's left, and current payout status. |
| my_contractsB | List all your contracts — active, completed, and expired. |
| registerA | Register a new user on Freeplay. Handles both immediate registration and waitlist. Returns user_id on success or waitlist position. |
| verify_identityA | Start KYC verification. Returns a Veriff session URL the user must complete, or instant verification with a sandbox passcode. |
| set_payout_methodA | Set how you want to get paid:
|
| statusB | Full account overview — registration status, KYC, payout method, active contracts, total earnings. |
| cash_outA | Cash out your pending earnings. All completed milestones accrue in your ledger. Once your pending balance reaches $5.00, you can withdraw everything at once. |
| recover_accountA | Recover your Freeplay account using your agent_id. Use this if you lost your user_id — your agent_id (the identifier you registered with) is all you need to get back in. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct action: browsing offers, getting offer details, accepting offers, checking contract progress, listing contracts, registering, verifying identity, setting payout methods, viewing account status, cashing out, and recovering accounts. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most tools follow a clear verb_noun pattern (browse_offers, get_offer, accept_offer, check_progress, verify_identity, set_payout_method, recover_account), but a few deviate (my_contracts, status, register, cash_out). These deviations are minor and do not impair readability.
With 11 tools, the server is well-scoped for the user lifecycle it manages—from registration and offer discovery to contract management, identity verification, payout setup, and cash-out. Each tool serves a necessary function without unnecessary duplication.
The tool set covers the full workflow: user registration, KYC verification, offer browsing/acquisition, contract status tracking, payout method selection, account status overview, and withdrawal. There are no obvious dead ends or missing core operations for the stated purpose.