L2 Calendar
NPM · L2CALENDAR-MCP · SCANNED SEP 25
Query Lineage 2 private server openings by chronicle through the public L2 Calendar API.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 427 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the L2 Calendar MCP server?
L2 Calendar runs locally as an npm package, launched with npx -y l2calendar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · l2calendar-mcp
claude mcp add dreiev-l2calendar-mcp -- npx -y l2calendar-mcp
{
"mcpServers": {
"dreiev-l2calendar-mcp": {
"command": "npx",
"args": [
"-y",
"l2calendar-mcp"
]
}
}
} {
"servers": {
"dreiev-l2calendar-mcp": {
"command": "npx",
"args": [
"-y",
"l2calendar-mcp"
]
}
}
} codex mcp add dreiev-l2calendar-mcp -- npx -y l2calendar-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dreiev-l2calendar-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"l2calendar-mcp"
],
"enabled": true
}
}
} openclaw mcp add dreiev-l2calendar-mcp --command npx --arg -y --arg l2calendar-mcp
mcp_servers:
dreiev-l2calendar-mcp:
command: "npx"
args: ["-y", "l2calendar-mcp"] {
"McpServers": {
"dreiev-l2calendar-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"l2calendar-mcp"
]
}
}
} assistant mcp add dreiev-l2calendar-mcp -t stdio -c npx -a -y l2calendar-mcp
{
"mcpServers": {
"dreiev-l2calendar-mcp": {
"command": "npx",
"args": [
"-y",
"l2calendar-mcp"
]
}
}
} 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.
- 25 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 56
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 25 Sept 2026 · Analysed npm/l2calendar-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_chronicles List Lineage 2 chronicles ~44
List every Lineage 2 chronicle tracked by L2 Calendar (slug, display name and order). Use the slugs as the chronicle filter for list_servers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_server Get a Lineage 2 private server ~66
Return the full public record of a single server by its exact name (case-insensitive), including description and labels.
| Name | Type | Req | Description |
|---|---|---|---|
| chronicle | string | – | Optional chronicle slug to narrow the lookup. |
| name | string | yes | Exact server name, for example "L2Hispano". |
No output schema declared.
No examples provided.
list_labels List server labels ~37
List the distinct labels (e.g. PTS, Low rate, Craft) currently applied to servers on the public page, with their colors.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_servers List Lineage 2 private servers ~199
List Lineage 2 private servers tracked by L2 Calendar, ordered by VIP status and opening date. Optionally filter by chronicle, upcoming openings, newly added entries or rate range.
| Name | Type | Req | Description |
|---|---|---|---|
| chronicle | string | – | Chronicle slug to filter by (e.g. interlude, high-five, classic, essence, god, gracia-final). Use get_chronicles for the full list. |
| limit | integer | – | Maximum number of servers to return (1-50). Defaults to 50, the API page size. |
| max_rate | number | – | Maximum numeric rate. GVE entries are excluded. |
| min_rate | number | – | Minimum numeric rate (e.g. 100 for x100+). GVE entries are excluded. |
| new_only | boolean | – | When true, only return servers flagged as newly added entries. |
| only_upcoming | boolean | – | When true, only return servers whose opening date is today or later. |
No output schema declared.
No examples provided.
search_servers Search Lineage 2 private servers ~81
Search the current L2 Calendar server page by free text. Matches the server name, website, rate, chronicle, description and labels (case-insensitive).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of matches to return (1-50). |
| query | string | yes | Text to match, for example "interlude x1000" or a server name. |
No output schema declared.
No examples provided.
What is the L2 Calendar MCP server?
L2 Calendar is an MCP server listed in the public MCP registry as io.github.Dreiev/l2calendar-mcp. Query Lineage 2 private server openings by chronicle through the public L2 Calendar API. This page covers its npm package (l2calendar-mcp).
Is the L2 Calendar MCP server safe to use?
L2 Calendar scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 L2 Calendar MCP server expose?
L2 Calendar exposes 5 tools: list_servers, get_chronicles, search_servers, get_server, list_labels. Their descriptions and schemas cost roughly 427 tokens of context every time the server is loaded.
Is the L2 Calendar MCP server still maintained?
L2 Calendar is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the L2 Calendar MCP server under?
L2 Calendar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.