Skip to main content
Glama
wangicheng

Online Judge MCP Server

by wangicheng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OJ_URLYesThe URL of the Orange Juice Online Judge API server (e.g., http://localhost:8000).
OJ_PASSWORDYesYour password for the Orange Juice Online Judge.
OJ_USERNAMEYesYour username for the Orange Juice Online Judge.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_problemsC

Fetch the list of problems from the Online Judge. Returns a JSON string containing total count and results.

list_my_submissionsC

Fetch the list of latest submissions made by the authenticated user. Returns a JSON string containing the submission histories.

get_problem_detailsB
Fetch the detailed information of a specific problem.
problem_id: The external ID/display ID of the problem (e.g., "PR-114-1-31").
submit_codeB
Submit code to the Online Judge for a specific problem.
problem_id: the internal system ID of the problem.
language: string such as "C", "C++", "Python3".
code: the source code to submit.
get_submission_statusB
Get the status and result of a previously submitted code.
submission_id: The ID returned when submitting the code.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: get_problem_details retrieves specific problem info, get_submission_status checks submission results, list_my_submissions shows user's submission history, list_problems lists available problems, and submit_code submits new code. The boundaries are well-defined and non-overlapping.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case: get_problem_details, get_submission_status, list_my_submissions, list_problems, and submit_code. The naming is predictable and readable throughout the set.

Tool Count5/5

With 5 tools, this server is well-scoped for an online judge domain. Each tool earns its place by covering core workflows: browsing problems, getting details, submitting code, and checking results. The count is neither too thin nor excessive for the purpose.

Completeness4/5

The toolset covers the essential CRUD-like operations for an online judge: list and get for problems, create (submit) for submissions, and get for submission status. A minor gap is the lack of a tool to delete or cancel submissions, but agents can work around this, and core workflows are well-supported.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources