AtCoder MCP Server
io.github.ketherworks/atcoderketherworksstreamable-httpv0.1.0Scanned
Search AtCoder problems and fetch public problem statements through MCP.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AtCoder MCP Server can do
The AtCoder MCP Server is published by the GitHub account ketherworks. It has 4 tools. It can create or change data (2 tools: oj_capabilities and oj_health), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (oj_fetch_problem and oj_search_problems).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
oj_capabilitiesReport the audited anonymous AtCoder read surface and explicitly unsupported operations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Report the audited anonymous AtCoder read surface and explicitly unsupported operations.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
oj_healthReport local readiness and the latest observed AtCoder page-read status without probing upstream.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Report local readiness and the latest observed AtCoder page-read status without probing upstream.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
oj_fetch_problemFetch one public problem statement from an exact contest/task pair or canonical atcoder.jp task URL.Reads text others writeNo findings
Why it is in this group
- The name "oj_fetch_problem" says "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch one public problem statement from an exact contest/task pair or canonical atcoder.jp task URL. Returns sanitized HTML with preserved math, samples, limits, hashes, and source provenance.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
oj_search_problemsResolve exactly one contest/task id, atcoder:contest/task id, or canonical task URL.Reads text others writeNo findings
Why it is in this group
- The name "oj_search_problems" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "resolve" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Resolve exactly one contest/task id, atcoder:contest/task id, or canonical task URL. Free-text and catalog crawling are not supported.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.ksrnyx.top/oj-mcp/atcoder/mcp: tools/list returned 4 tools to an anonymous client, including oj_capabilities (write), oj_health (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http atcoder https://api.ksrnyx.top/oj-mcp/atcoder/mcpclaude mcp add --transport http atcoder https://api.ksrnyx.top/oj-mcp/atcoder/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__atcoder__oj_fetch_problem",
"mcp__atcoder__oj_search_problems"
],
"ask": [
"mcp__atcoder__oj_capabilities",
"mcp__atcoder__oj_health"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as atcoder. Review it before you use it.
Capability tags behind 2 rules
- mcp__atcoder__oj_fetch_problem untrusted-input
- mcp__atcoder__oj_search_problems untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ketherworks/atcoder/verify?hash=8264073c63be8f0413d5bb845f50e6a2f99b278317cdc2986b34a32f37005424" | jq -e '.changed == false'Pinned hash 8264073c63be, from Nov 20, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ketherworks/atcoder/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ketherworks/atcoder)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
AtCoder MCP Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AtCoder MCP Server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AtCoder MCP Server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AtCoder MCP Server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AtCoder MCP Server have?
- 4 tools: 2 write, 2 read. oj_capabilities, oj_health, oj_fetch_problem and oj_search_problems.
Does the AtCoder MCP Server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AtCoder MCP Server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AtCoder MCP Server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.