Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / Codeforces MCP Server

Search Codeforces problems and inspect public problem metadata through the official Codeforces API.

Answered:

2 of 4 checks

Status
no response
Typical response time
304 ms
Last checked
Latest check:
This server answered in an earlier check. At its latest check it was: no response.Last checked  · MCP initialize · 8s limit · HTTP 500 · the call took 101 ms.
Address
https://codeforces-oj-mcp.lantangtang54.workers.dev/mcp
Listed in:
official MCP registry mcp_registry
Registry name
io.github.ketherworks/codeforces
Transport
streamable HTTP streamable-http
Host
codeforces-oj-mcp.lantangtang54.workers.dev

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

Check history

oldest to newest; each row is one recorded check
Recorded checks for Codeforces MCP Server
CheckedStatusTookCheck
responds198 msMCP initialize · 8s limit · HTTP 200
responds410 msMCP initialize · 8s limit · HTTP 200
no response56 msMCP initialize · 8s limit · HTTP 500
no response101 msMCP initialize · 8s limit · HTTP 500

Ask for a working one

This server is not answering right now. Say what you needed from it. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.