MCP server for Codeforces Polygon API
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"polygon-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Polygon MCP Server MCP server for Polygon API (Codeforces Polygon). ## Requirements - Python 3.10+ - `polygon_api==1.2.0` ## Install ### From PyPI repository ```bash pip install polygon-mcp-server ``` With uv: ```bash uv pip install polygon-mcp-server ``` ### From the sources Install the package (adds the `polygon-mcp` CLI): ```bash pip install . ``` With uv: ```bash uv pip install . ``` Or install the CLI tool into uv's tool environment: ```bash uv tool install . ``` ## Run Set credentials: - `POLYGON_API_KEY` - `POLYGON_API_SECRET` - Optional: `POLYGON_API_URL` - Optional: `POLYGON_MCP_CONFIG` to load stored credentials Then start: ```bash polygon-mcp ``` ## Logging Logs are written to `~/.local/state/polygon-mcp/polygon-mcp.log` (or `$XDG_STATE_HOME/polygon-mcp/polygon-mcp.log` if set). Override with `POLYGON_MCP_LOG_FILE`. ## File output safety Tools that write to disk only allow paths within: - the current project directory - `/tmp` - any extra roots in `POLYGON_MCP_OUTPUT_ROOTS` (colon-separated)
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.