_ registry / mcp streamable-http · checked 3h ago

l2tools

https://l2tools.org

Registry code: de086ec87ab35506

api record

Read-only Lineage 2 reference data. Always preserve the requested chronicle and include dataset provenance in answers.

endpoint
https://l2tools.org/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is l2tools live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is l2tools free to use?
Yes — the hub reached it with no key and no payment.
What tools does l2tools have?
5 tools: get_npc_drops, search_npcs, get_xp_levels, get_npc, get_soul_crystal_progression.
Is l2tools safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
408ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 273 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
games & entertainment games
used for
  • look up a lineage 2 npc
  • get npc drop and spoil chances
  • get experience per level
  • get soul crystal progression
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_npc_drops reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "chronicle",
    "npcId"
  ],
  "properties": {
    "npcId": {
      "type": "integer",
      "minimum": 1
    },
    "chronicle": {
      "enum": [
        "interlude",
        "high-five"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • search_npcs reads unknown 26h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "chronicle",
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2
    },
    "chronicle": {
      "enum": [
        "interlude",
        "high-five"
      ],
      "type": "string",
      "description": "Exact chronicle namespace."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • get_xp_levels reads unknown 16h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "chronicle",
    "fromLevel",
    "toLevel"
  ],
  "properties": {
    "toLevel": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    },
    "chronicle": {
      "enum": [
        "interlude",
        "high-five"
      ],
      "type": "string"
    },
    "fromLevel": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • get_npc reads unknown 26h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "chronicle",
    "npcId"
  ],
  "properties": {
    "npcId": {
      "type": "integer",
      "minimum": 1
    },
    "chronicle": {
      "enum": [
        "interlude",
        "high-five"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_soul_crystal_progression reads unknown 26h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "chronicle",
    "npcId"
  ],
  "properties": {
    "npcId": {
      "type": "integer",
      "minimum": 1
    },
    "chronicle": {
      "enum": [
        "interlude",
        "high-five"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id de086ec87ab35506.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/de086ec87ab35506/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/de086ec87ab35506/badge.svg)](https://brick.blue/agent/de086ec87ab35506?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.