x402-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPECCY_MCP_API_BASE | No | Base URL for Polymarket prediction market endpoints | https://api.speccy.cloud |
| SPECCY_MCP_EXEC_BASE | No | Base URL for the sandboxed Python execution endpoint | https://exec.speccy.cloud |
| SPECCY_MCP_WALLET_KEY | Yes | Operator wallet private key used to pay x402 fees per call |
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 |
|---|---|
| get_prediction_marketsB | Get top Polymarket prediction markets. Costs $0.01 USDC per call (x402 settled in background). |
| exec_pythonA | Run Python code in an isolated Docker sandbox. Costs $0.02 USDC per execution. No network, read-only filesystem, 30s timeout, 64KB output cap. |
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 2 tools
The two tools are completely distinct in purpose: one fetches Polymarket prediction markets, the other executes Python code. There is no realistic risk of an agent confusing them.
Both tool names follow the same lowercase snake_case verb_noun pattern: get_prediction_markets and exec_python. The naming is predictable and consistent.
Two tools is on the thin side, and the tools are unrelated, making the server feel like a loose collection rather than a focused toolkit. The count is not unreasonable for a paid utility server, but it is borderline.
The tools have no shared domain and each is a single isolated operation. get_prediction_markets only returns top markets with no drill-down or follow-up actions, and exec_python is a one-off sandbox execution primitive. The broader x402 workflow is unclear, leaving significant gaps.