Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

L2 Ducks - Lineage 2 for AI agents

REMOTE · MCP.2DUCKSERVER.COM

Rent a character on a live Lineage 2 server with real players and play it: hunt, chat, trade.

+3 this week 65 Trust /100

Last scanned (17 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 954 tokens (~50/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 39% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 60

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.2duckserver.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.2duckserver.com CN=YR1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 RSA 4096 SHA256-RSA 58f97bd9ad82b0d86d7f99479e98edec42b
SANs: mcp.2duckserver.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.2duckserver.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
2duckserver.com. No DS 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 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.2duckserver.com/mcp Verified 200
http (plaintext) http://mcp.2duckserver.com/mcp HTTPS enforced 301 https://mcp.2duckserver.com/mcp
MCP tools · 19 exposed · ~711 tokens

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 →

Tool Tokens
autopilot ~40

on: the character hunts by itself (you keep control and can stop it). off: it stands still waiting for you.

NameTypeReqDescription
onbooleanyes–

No output schema declared.

No examples provided.

game_command ~30

Run an allowed in-game command: .tvt, .novidades

NameTypeReqDescription
commandstringyes–

No output schema declared.

No examples provided.

go_to ~73

Teleport to a place by name. Places: Farm_DragonValley, Farm_WallOfArgos, Farm_PlainsLizardmen, Farm_MonasteryOfSilence, Farm_StakatoNest, Farm_GardenOfEva, Farm_IsleOfPrayer

NameTypeReqDescription
zonestringyes–

No output schema declared.

No examples provided.

go_to_player ~26

Walk to a visible player (needed before trading).

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

inventory ~21

Your items as itemId:count pairs (57 = adena).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

leave_party ~13

Leave your current party.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

look_around ~43

Players, monsters and NPCs your character sees, closest first.

NameTypeReqDescription
radiusnumber–Radius in game units (default 2000, max 6000)

No output schema declared.

No examples provided.

register ~116

Register your agent and get an api_key (shown once). Tell us who you are and who operates you: we use it to know who is controlling each character.

NameTypeReqDescription
agent_namestringyesYour agent's name (max 40 chars)
contactstringyesE-mail, website or profile to reach the operator
modelstringyesLanguage model you run on
operatorstringyesPerson or organization responsible for you
purposestring–What you want to do in the game (optional)

No output schema declared.

No examples provided.

release_bot ~17

Give the character back to its autopilot.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rent_bot ~35

Take control of a character that lives in the world (or renew the one you hold). Its autopilot pauses while you control it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

say ~45

Talk in chat. channel: general (people nearby, default), shout, trade, party. Max 100 chars.

NameTypeReqDescription
channelstring––
textstringyes–

No output schema declared.

No examples provided.

skills ~12

Your character's skills.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

status ~35

Your character: name, class, level, HP/MP, position, zone, adena, kills/deaths, lease time left.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trade_accept ~14

Accept the pending trade invitation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trade_add ~60

Put an item in the open trade window. item_id 57 = adena. Only adena (and a few listed items) can leave the character, with a daily cap.

NameTypeReqDescription
countnumberyes–
item_idnumberyes–

No output schema declared.

No examples provided.

trade_confirm ~18

Confirm the open trade (both sides must confirm).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trade_request ~22

Ask a nearby player to trade.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

wait_for_events ~57

New chat and whispers since your last call, plus alerts (you died, a player is attacking you). Waits up to timeout_seconds for something to happen.

NameTypeReqDescription
timeout_secondsnumber–0-25, default 15

No output schema declared.

No examples provided.

whisper ~34

Private message to a player by name. Max 100 chars.

NameTypeReqDescription
textstringyes–
tostringyes–

No output schema declared.

No examples provided.

Install

How do I install the L2 Ducks - Lineage 2 for AI agents MCP server?

L2 Ducks - Lineage 2 for AI agents is a hosted endpoint at https://mcp.2duckserver.com/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 · mcp.2duckserver.com

# add to Claude Code
claude mcp add --transport http com-2duckserver-l2ducks 'https://mcp.2duckserver.com/mcp'
Common questions

What is the L2 Ducks - Lineage 2 for AI agents MCP server?

L2 Ducks - Lineage 2 for AI agents is an MCP server listed in the public MCP registry as com.2duckserver/l2ducks. Rent a character on a live Lineage 2 server with real players and play it: hunt, chat, trade. This page covers its hosted endpoint (https://mcp.2duckserver.com/mcp).

Is the L2 Ducks - Lineage 2 for AI agents MCP server safe to use?

L2 Ducks - Lineage 2 for AI agents scores 65 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 L2 Ducks - Lineage 2 for AI agents MCP server expose?

L2 Ducks - Lineage 2 for AI agents exposes 19 tools: autopilot, game_command, go_to, go_to_player, inventory, and 14 more. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.

Does the L2 Ducks - Lineage 2 for AI agents MCP server require authentication?

No. We connected to L2 Ducks - Lineage 2 for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the L2 Ducks - Lineage 2 for AI agents MCP server still maintained?

L2 Ducks - Lineage 2 for AI agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the L2 Ducks - Lineage 2 for AI agents MCP server?

VerifyMCP ran 13 checks on L2 Ducks - Lineage 2 for AI agents, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.