question-market
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KMD_PORT | No | LocalNet KMD port. Default: 4002 | |
| KMD_TOKEN | No | LocalNet KMD token. Default: 64 × a | |
| ALGOD_PORT | No | Algorand node port. Default: 443 | |
| FAUCET_URL | No | Override the faucet endpoint for request_testnet_tokens. Default: https://question.market/api/faucet | |
| KMD_SERVER | No | LocalNet KMD URL. Default: http://localhost | |
| ALGOD_TOKEN | No | Algorand node auth token. Default: empty | |
| INDEXER_URL | No | question.market API endpoint. Default: https://question.market/api | |
| USDC_ASA_ID | No | USDC ASA ID. Required for trading, LP, claims, refunds, and USDC-aware balances. Auto-loaded from bundled deployment. | |
| ALGOD_SERVER | No | Algorand node URL. Default: https://testnet-api.4160.nodely.dev | |
| INDEXER_AUTH | No | Optional basic-auth credentials for self-hosted indexers. | |
| AGENT_MNEMONIC | No | 25-word mnemonic preloaded as the signer for write tools. | |
| FACTORY_APP_ID | No | MarketFactory application ID. Required for create_market. Auto-loaded from bundled deployment. | |
| INDEXER_WRITE_TOKEN | No | Optional bearer token used only by create_market. | |
| PROTOCOL_CONFIG_APP_ID | No | ProtocolConfig application ID. Required for create_market. Auto-loaded from bundled deployment. | |
| QUESTION_MARKET_NETWORK | No | Force network selection (testnet, mainnet, or localnet). | |
| QUESTION_MARKET_DEPLOYMENT_OUT | No | Same as above, used by some deploy scripts. | |
| QUESTION_MARKET_DEPLOYMENT_PATH | No | Override path to a protocol-deployment.json. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| question_marketA | Overview of the question.market MCP server: available tools, onboarding flow, and links. |
| list_marketsA | List prediction markets. Filter by status: 0=CREATED, 1=ACTIVE, 2=RESOLUTION_PENDING, 3=RESOLUTION_PROPOSED, 4=CANCELLED, 5=RESOLVED, 6=DISPUTED |
| get_marketA | Get detailed market state: prices, pool, outcomes, deadline, resolution status. |
| get_market_tradesC | Get recent trades for a market. |
| get_price_historyC | Get historical price snapshots for charting. |
| get_positionsA | Get all positions for a wallet address across all markets. |
| get_current_holdingsA | Get a wallet's current holdings with per-market positions, LP stakes, marked value, and claimable resolved exposure. |
| get_market_positionsC | Get all user positions in a specific market. |
| get_leaderboardA | Get the leaderboard: wallets ranked by realized trading PnL from closed positions. |
| create_walletA | Generate a new Algorand account. Returns address and mnemonic. Call set_wallet with the mnemonic to activate it for trading. |
| set_walletA | Activate a wallet for this MCP connection. All write tools will sign with this account until the connection closes or set_wallet is called again. Overrides the wallet_index parameter on all tools. No restart needed. |
| request_testnet_tokensA | Fund the active session wallet (or a specified address) with testnet ALGO and tUSDC in one call. When the address is omitted or matches the active session wallet, the MCP also signs the tUSDC opt-in automatically and calls the faucet a second time so the wallet ends up with both ALGO and tUSDC. ALGO drips are capped at one per wallet / IP every 24 hours; tUSDC at one per wallet every hour. If a third-party address is passed, the MCP can only request the ALGO drip and returns optIn:true — that wallet's owner must sign the opt-in themselves. |
| get_balanceA | Check ALGO and tUSDC balance for an address. Defaults to the active session wallet if address is omitted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| market |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qmrkt/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server