TokenKnows vs AtCoder MCP Server
TokenKnows is an MCP server published by johnnywuj81. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). AtCoder MCP Server is an MCP server published by ketherworks. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  TokenKnows |  AtCoder MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Downloads/month (PyPI): 88 Downloads/week (PyPI): 23 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | TokenKnows | AtCoder MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (tokenknows-mcp) | Remote server (api.ksrnyx.top/oj-mcp/atcoder/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 4 | Not published |
| Parts of the bundle (differs) | 12 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/johnnywuj81/tokenknows | github.com/ketherworks/atcoder-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 40 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
TokenKnows
Distill AI coding sessions into weekly reports, ADRs and a knowledge graph - self-hosted
AtCoder MCP Server
Search AtCoder problems and fetch public problem statements through MCP.
How to run each
TokenKnows As a local MCP server: PyPI package
claude mcp add --env "TOKENKNOWS_API_TOKEN=<YOUR_TOKENKNOWS_API_TOKEN>" --transport stdio tokenknows -- uvx tokenknows-mcpRequires: TOKENKNOWS_API_TOKEN (secret)
AtCoder MCP Server As a remote MCP server
claude mcp add --transport http atcoder https://api.ksrnyx.top/oj-mcp/atcoder/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only AtCoder MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of AtCoder MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: TokenKnows · What it can do: AtCoder MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.