# L2Tools — Lineage 2 Reference Data (remote · l2tools.org)

Read-only Interlude and High Five NPC, loot, Soul Crystal and XP reference tools.

- Trust score: 82/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- remote · `l2tools.org`: 82/100 (this document), [markdown](https://verifymcp.io/servers/maxence-l2tools/api-mcp.md), [page](https://verifymcp.io/servers/maxence-l2tools/api-mcp)

## Channel facts

- Endpoint: `https://l2tools.org/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-01.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 258 tokens (~51/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 8% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the L2Tools — Lineage 2 Reference Data MCP server?

L2Tools — Lineage 2 Reference Data is a hosted endpoint at https://l2tools.org/api/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.

### Claude

```bash
claude mcp add --transport http maxence-l2tools 'https://l2tools.org/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "maxence-l2tools": {
      "url": "https://l2tools.org/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "maxence-l2tools": {
      "type": "http",
      "url": "https://l2tools.org/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.maxence-l2tools]
url = "https://l2tools.org/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maxence-l2tools": {
      "type": "remote",
      "url": "https://l2tools.org/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add maxence-l2tools --url 'https://l2tools.org/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  maxence-l2tools:
    url: "https://l2tools.org/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "maxence-l2tools": {
      "Transport": "http",
      "Url": "https://l2tools.org/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add maxence-l2tools -t streamable-http -u 'https://l2tools.org/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "maxence-l2tools": {
      "type": "http",
      "url": "https://l2tools.org/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 82, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 82, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `search_npcs` (~52 tokens)

Search Lineage 2 NPCs

Search chronicle-scoped NPCs by name or numeric ID before opening a record.

Input parameters:

- `chronicle` (string, required): Exact chronicle namespace.
- `limit` (integer)
- `query` (string, required)

### `get_npc` (~41 tokens)

Get an NPC record

Get stats, traits, skills, locations and provenance for one numeric NPC ID.

Input parameters:

- `chronicle` (string, required)
- `npcId` (integer, required)

### `get_npc_drops` (~41 tokens)

Get NPC x1 drops

Get effective x1 drop and spoil probabilities for one numeric NPC ID.

Input parameters:

- `chronicle` (string, required)
- `npcId` (integer, required)

### `get_soul_crystal_progression` (~52 tokens)

Get Soul Crystal progression

Get Soul Crystal result stages, transitions and chances for one NPC. Result stage N means N-1 to N.

Input parameters:

- `chronicle` (string, required)
- `npcId` (integer, required)

### `get_xp_levels` (~47 tokens)

Get XP levels

Get per-level and cumulative experience values for an inclusive level range.

Input parameters:

- `chronicle` (string, required)
- `fromLevel` (integer, required)
- `toLevel` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/maxence-l2tools/api-mcp#diagnostics

## Score history

- 2026-10-01: 82
- 2026-09-30: 82
- 2026-09-29: 82
- 2026-09-28: 82
- 2026-09-27: 82
- 2026-09-26: 82
- 2026-09-25: 82
- 2026-09-24: 81
- 2026-09-23: 81
- 2026-09-22: 80
- 2026-09-21: 80
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 74
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 71

## Common questions

### What is the L2Tools — Lineage 2 Reference Data MCP server?

L2Tools — Lineage 2 Reference Data is an MCP server listed in the public MCP registry as io.github.Maxence/l2tools. Read-only Interlude and High Five NPC, loot, Soul Crystal and XP reference tools. This page covers its hosted endpoint (https://l2tools.org/api/mcp).

### Is the L2Tools — Lineage 2 Reference Data MCP server safe to use?

L2Tools — Lineage 2 Reference Data scores 82 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 L2Tools — Lineage 2 Reference Data MCP server expose?

L2Tools — Lineage 2 Reference Data exposes 5 tools: search_npcs, get_npc, get_npc_drops, get_soul_crystal_progression, get_xp_levels. Their descriptions and schemas cost roughly 233 tokens of context every time the server is loaded.

### Does the L2Tools — Lineage 2 Reference Data MCP server require authentication?

No. We connected to L2Tools — Lineage 2 Reference Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the L2Tools — Lineage 2 Reference Data MCP server still maintained?

L2Tools — Lineage 2 Reference Data is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://l2tools.org/api/mcp
- Website: https://l2tools.org/developers
- Changelog RSS feed: https://verifymcp.io/servers/maxence-l2tools/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/maxence-l2tools/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/maxence-l2tools/api-mcp