Codeforces Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

Codeforces competitive programming API: contests and user info. No key required.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant query Codeforces competitive programming data such as contests and user information through a local MCP server.

What you can do
Wraps the Codeforces competitive programming API so an assistant can look up contests and user information. It is a local stdio server distributed as the npm package codeforces-mcp. No tools are listed in the manifest, so the exact tool set is not documented here.
When to use it
Useful when you want an assistant to pull Codeforces contest or user details during competitive programming work, without leaving the chat. It is a narrow, single-source integration, so it is only worth adding if Codeforces data is what you need.
Requirements
Runs as a local process on the user's machine via the npm package codeforces-mcp over stdio. Node.js is needed to run the package. No API key, environment variables, or headers are declared. Desktop only; not available as a web executable.
Before you install
The registry description states no key is required, and no credentials, environment variables, or headers are declared. No write, send, or delete actions are described. The manifest lists no tools, so review the actual tool set before installing.

Installation

In SourceWeft

  1. Open Codeforces Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.