Luogu MCP Server
REMOTE · LUOGU-MCP-SERVER.LANTANGTANG54.WORKERS.DEV · SCANNED SEP 20
Search Luogu problems, fetch statements, explore problem sets and get practice recommendations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 500, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Luogu MCP Server server?
Luogu MCP Server is a hosted endpoint at https://luogu-mcp-server.lantangtang54.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · luogu-mcp-server.lantangtang54.workers.dev
claude mcp add --transport http kaiserunix-luogu-mcp-server 'https://luogu-mcp-server.lantangtang54.workers.dev/mcp'
{
"mcpServers": {
"kaiserunix-luogu-mcp-server": {
"url": "https://luogu-mcp-server.lantangtang54.workers.dev/mcp"
}
}
} {
"servers": {
"kaiserunix-luogu-mcp-server": {
"type": "http",
"url": "https://luogu-mcp-server.lantangtang54.workers.dev/mcp"
}
}
} [mcp_servers.kaiserunix-luogu-mcp-server] url = "https://luogu-mcp-server.lantangtang54.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kaiserunix-luogu-mcp-server": {
"type": "remote",
"url": "https://luogu-mcp-server.lantangtang54.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add kaiserunix-luogu-mcp-server --url 'https://luogu-mcp-server.lantangtang54.workers.dev/mcp' --transport streamable-http
mcp_servers:
kaiserunix-luogu-mcp-server:
url: "https://luogu-mcp-server.lantangtang54.workers.dev/mcp" {
"McpServers": {
"kaiserunix-luogu-mcp-server": {
"Transport": "http",
"Url": "https://luogu-mcp-server.lantangtang54.workers.dev/mcp"
}
}
} assistant mcp add kaiserunix-luogu-mcp-server -t streamable-http -u 'https://luogu-mcp-server.lantangtang54.workers.dev/mcp'
{
"mcpServers": {
"kaiserunix-luogu-mcp-server": {
"type": "http",
"url": "https://luogu-mcp-server.lantangtang54.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.40 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://luogu-mcp-server.lantangtang54.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lantangtang54.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 63b50129715a6c7f22bbbda7e664c2f8c65 |
| SANs: *.lantangtang54.workers.dev, lantangtang54.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of luogu-mcp-server.lantangtang54.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 500 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://luogu-mcp-server.lantangtang54.workers.dev/mcp | HTTP error | 500 | |
| http (plaintext) | http://luogu-mcp-server.lantangtang54.workers.dev/mcp | Inconclusive | 500 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
luogu_fetch_problem Fetch Luogu Problem ~64
Fetch a Luogu problem statement, formats, samples, tags, difficulty, and source URL by pid.
| Name | Type | Req | Description |
|---|---|---|---|
| maxStatementChars | integer | – | Trim long statements for model context control. |
| pid | string | yes | Luogu problem id, such as P1305. |
No output schema declared.
No examples provided.
luogu_fetch_problem_set Fetch Luogu Training Set ~52
Fetch a Luogu training/problem set and its problem summaries by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Luogu training id, such as 100. |
| limit | integer | – | Maximum returned problem summaries. |
No output schema declared.
No examples provided.
luogu_find_related_problems Find Related Luogu Problems ~138
Find related Luogu practice problems by mixing topic/pain-point recommendations with live keyword search.
| Name | Type | Req | Description |
|---|---|---|---|
| currentProblemId | string | – | Exclude this current Luogu problem id. |
| limit | integer | – | Maximum returned related problems. |
| painPoint | string | – | Student pain point such as traversal_order_confusion or sentinel_input. |
| pid | string | – | Current Luogu problem id, used for context and exclusion in future versions. |
| query | string | – | Free-text query, title fragment, or topic phrase. |
| topic | string | – | Topic such as binary_tree, recursion, matrix, output_format, tree_distance. |
No output schema declared.
No examples provided.
luogu_find_topic_problems Find Luogu Topic Problems ~95
Find Luogu practice problems for an algorithm topic using aliases, known Luogu tag ids, deduplication, and match reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeProblemIds | array | – | Luogu problem ids to exclude from recommendations. |
| limit | integer | – | Maximum returned items. |
| topic | string | yes | Algorithm topic or alias, such as SPFA, Prim, Treap, 二叉树, or 动态规划. |
No output schema declared.
No examples provided.
luogu_get_capabilities Get Luogu Route Capabilities ~31
Report which LeetCode-style route capabilities are available, auth-required, or planned for Luogu.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
luogu_get_user_profile Get Luogu User Profile ~32
Fetch public Luogu user profile data by uid.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | integer | yes | Luogu user id. |
No output schema declared.
No examples provided.
luogu_list_algorithm_topics List Luogu Algorithm Topics ~33
List canonical algorithm topics, aliases, and known Luogu tag ids used by the high-level topic search route.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
luogu_recommend_problems Recommend Luogu Problems ~101
Recommend seed Luogu problems from a topic or student pain point, with search hints for further exploration.
| Name | Type | Req | Description |
|---|---|---|---|
| currentProblemId | string | – | Exclude this current Luogu problem id. |
| limit | integer | – | Maximum returned recommendations. |
| painPoint | string | – | Student pain point such as traversal_order_confusion or sentinel_input. |
| topic | string | – | Topic such as binary_tree, recursion, matrix, output_format, tree_distance. |
No output schema declared.
No examples provided.
luogu_resolve_problem Resolve Luogu Problem ~72
Resolve a Luogu problem from a URL, problem id, or title fragment, then fetch the problem details.
| Name | Type | Req | Description |
|---|---|---|---|
| maxStatementChars | integer | – | Trim long statements for model context control. |
| query | string | yes | Luogu URL, pid such as P1305, or title/keyword fragment. |
No output schema declared.
No examples provided.
luogu_search_problem_sets Search Luogu Training Sets ~109
Search Luogu training/problem sets by keyword. By default, combines title-filtered official sets with selected user-shared sets.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Training set keyword or title fragment. |
| limit | integer | – | Maximum returned items. |
| page | integer | – | Luogu training list page, starting from 1. |
| type | string | – | Search scope: all combines official and selected sets; official filters Luogu official sets by title; select searches selected user-shared sets. |
No output schema declared.
No examples provided.
luogu_search_problems Search Luogu Problems ~104
Search Luogu problems by keyword. Use this before fetching a problem when you only know a topic or partial title.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Keyword, topic, title fragment, or problem id. |
| limit | integer | – | Maximum returned items. |
| page | integer | – | Luogu list page, starting from 1. |
| tagIds | array | – | Optional Luogu tag ids to narrow topic search, such as [11] for tree-related searches. |
No output schema declared.
No examples provided.
What is the Luogu MCP Server server?
Luogu MCP Server is listed in the public MCP registry as io.github.Kaiserunix/luogu-mcp-server. Search Luogu problems, fetch statements, explore problem sets and get practice recommendations. This page covers its hosted endpoint (https://luogu-mcp-server.lantangtang54.workers.dev/mcp).
Is the Luogu MCP Server server safe to use?
Luogu MCP Server scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Luogu MCP Server server expose?
Luogu MCP Server exposes 11 tools: luogu_search_problems, luogu_fetch_problem, luogu_resolve_problem, luogu_find_related_problems, luogu_list_algorithm_topics, and 6 more. Their descriptions and schemas cost roughly 831 tokens of context every time the server is loaded.
Does the Luogu MCP Server server require authentication?
No. We connected to Luogu MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Luogu MCP Server server still maintained?
Luogu MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.