# io.github.Web3kaneco/lazy-lions-mcp (npm · lazy-lions-mcp)

Read the Lazy Lions NFT ecosystem: tokens, traits, rarity, holders, and the $LAZY economy.

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `lazy-lions-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/web3kaneco-lazy-lions-mcp/lazy-lions-mcp.md), [page](https://verifymcp.io/servers/web3kaneco-lazy-lions-mcp/lazy-lions-mcp)

## Channel facts

- Registry: `npm`
- Package: `lazy-lions-mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 30 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1450 tokens (~80/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 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 io.github.Web3kaneco/lazy-lions-mcp server?

io.github.Web3kaneco/lazy-lions-mcp runs locally as an npm package, launched with npx -y lazy-lions-mcp. 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 web3kaneco-lazy-lions-mcp -- npx -y lazy-lions-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "web3kaneco-lazy-lions-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lazy-lions-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "web3kaneco-lazy-lions-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lazy-lions-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add web3kaneco-lazy-lions-mcp -- npx -y lazy-lions-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "web3kaneco-lazy-lions-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lazy-lions-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add web3kaneco-lazy-lions-mcp --command npx --arg -y --arg lazy-lions-mcp
```

### Hermes

```yaml
mcp_servers:
  web3kaneco-lazy-lions-mcp:
    command: "npx"
    args: ["-y", "lazy-lions-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "web3kaneco-lazy-lions-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lazy-lions-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add web3kaneco-lazy-lions-mcp -t stdio -c npx -a -y lazy-lions-mcp
```

### Other

```json
{
  "mcpServers": {
    "web3kaneco-lazy-lions-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lazy-lions-mcp"
      ]
    }
  }
}
```

## 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-20 (score 77, −3)

- [functional] Stability: pass → 0.80

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

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 79, +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-15 (score 78, +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-13 (score 77, +1)

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

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

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

### 2026-09-09 (score 75, +1)

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

### 2026-09-06 (score 74, +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 (18)

### `search_tokens` (~165 tokens)

Search or filter Lions/Cubs by traits, sale status, and unlock status. Use this for questions like 'which Lions have a Crown', 'show me Cubs for sale under 0.1 ETH', or 'how many Lions have blue eyes'. Returns paginated tokens with their traits and listing state.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.
- `for_sale` (boolean): Only tokens currently listed for sale.
- `limit` (integer): Results per page (max 100).
- `offset` (integer): Pagination offset.
- `traits` (string): Trait filter as JSON, e.g. {"Headgear":"Crown","Eyes":"Laser"}. Trait names are case-sensitive.

### `smart_search` (~109 tokens)

Natural-language search over the collection. Give it a plain-English request like 'lions with a crown and laser eyes that are for sale' and it resolves the traits and filters for you. Prefer this when the user's phrasing is fuzzy; use search_tokens when you already know exact trait names.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.
- `query` (string, required): Natural-language description of the tokens to find.

### `get_token` (~88 tokens)

Full detail for one Lion or Cub by token number: traits, rarity rank, current owner, listing status, and unlock state (butt / front face for Lions).

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.
- `token_id` (integer, required): On-chain token number, e.g. 1922.

### `get_traits` (~76 tokens)

The full trait catalog for a collection: every trait type, its possible values, and how many tokens carry each. Use this to learn valid trait names before calling search_tokens, or to answer rarity questions.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.

### `get_rarity` (~70 tokens)

Rarity scores and ranks for a token, blending trait rarity with market signals (last sale, current ask).

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.
- `token_id` (integer, required): On-chain token number.

### `get_floors` (~50 tokens)

Current floor price for a collection, plus the cheapest listed token.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.

### `get_listings` (~71 tokens)

Tokens currently listed for sale, with prices and marketplace links.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.
- `limit` (integer): Results per page (max 100).
- `offset` (integer): Pagination offset.

### `get_collection_stats` (~55 tokens)

Headline stats for the ecosystem: supply, unique holders, listed counts, and unlock totals.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.

### `get_holder` (~77 tokens)

Everything a wallet owns across the ecosystem — Lions, Cubs, and Generals — aggregated across all of that holder's linked wallets. Accepts an address or a Lazy Lions username.

Input parameters:

- `address` (string, required): Wallet address (0x...) or Lazy Lions username.
- `include_linked` (boolean): Aggregate across the holder's linked wallets.

### `get_holder_profile` (~47 tokens)

Public profile for a holder: username, bio, avatar, holdings summary, and earned Pride Mark badges.

Input parameters:

- `address` (string, required): Wallet address (0x...) or Lazy Lions username.

### `get_leaderboard` (~47 tokens)

Top holders ranked by total NFTs, Lions, Cubs, or badges earned.

Input parameters:

- `limit` (integer): How many holders to return.
- `sort_by` (string): Ranking metric.

### `get_lazy_market` (~30 tokens)

Live $LAZY market data on Base: price, 24h change, volume, and liquidity.

### `get_lazy_protocol` (~45 tokens)

Ecosystem-wide $LAZY snapshot: total supply, burned (verified against the on-chain dead-address balance), circulating, locked, pending unlock, and the count of active lockers.

### `get_lazy_balance` (~61 tokens)

A wallet's $LAZY position: liquid balance plus any amount locked on-chain, optionally aggregated across the holder's linked wallets.

Input parameters:

- `address` (string, required): Wallet address (0x...).
- `include_linked` (boolean): Aggregate across linked wallets.

### `get_lazy_leaderboard` (~72 tokens)

$LAZY leaderboards: wallets ranked by total tokens burned, or by amount currently locked on-chain.

Input parameters:

- `address` (string): Optional: return just this wallet's rank and totals.
- `board` (string): Which leaderboard to read.
- `limit` (integer): How many wallets to return.

### `get_lazy_burns` (~97 tokens)

Individual $LAZY burn events, newest first, each with transaction hash and Basescan link. Cub rerolls burn $LAZY, so this doubles as a live feed of reroll activity.

Input parameters:

- `address` (string): Filter to one burner wallet.
- `limit` (integer): How many events (max 200).
- `since` (string): ISO timestamp — only events at or after it. Use for incremental polling.

### `get_token_history` (~98 tokens)

History for one token: ownership transfers, and for Cubs the full reroll history showing how its art and traits changed over time.

Input parameters:

- `collection` (string): Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs.
- `kind` (string): 'transfers' for ownership history, 'rerolls' for Cub reroll history.
- `token_id` (integer, required): On-chain token number.

### `get_recent_changes` (~76 tokens)

Recent ecosystem activity feed: ownership changes, listings, rerolls, and unlocks since a timestamp. Use this to monitor the collection rather than repeatedly re-reading full lists.

Input parameters:

- `since` (string): ISO timestamp to read changes from.
- `types` (string): Comma-separated filter, e.g. 'reroll,transfer'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/web3kaneco-lazy-lions-mcp/lazy-lions-mcp#diagnostics

## Score history

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

## Common questions

### What is the io.github.Web3kaneco/lazy-lions-mcp server?

io.github.Web3kaneco/lazy-lions-mcp is listed in the public MCP registry as io.github.Web3kaneco/lazy-lions-mcp. Read the Lazy Lions NFT ecosystem: tokens, traits, rarity, holders, and the $LAZY economy. This page covers its npm package (lazy-lions-mcp).

### Is the io.github.Web3kaneco/lazy-lions-mcp server safe to use?

io.github.Web3kaneco/lazy-lions-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 io.github.Web3kaneco/lazy-lions-mcp server expose?

io.github.Web3kaneco/lazy-lions-mcp exposes 18 tools: search_tokens, smart_search, get_token, get_traits, get_rarity, and 13 more. Their descriptions and schemas cost roughly 1,334 tokens of context every time the server is loaded.

### Is the io.github.Web3kaneco/lazy-lions-mcp server still maintained?

io.github.Web3kaneco/lazy-lions-mcp 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.

### What licence is the io.github.Web3kaneco/lazy-lions-mcp server under?

io.github.Web3kaneco/lazy-lions-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/lazy-lions-mcp
- Socket report: https://socket.dev/npm/package/lazy-lions-mcp
- Website: https://lazylionsnft.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/web3kaneco-lazy-lions-mcp/lazy-lions-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/web3kaneco-lazy-lions-mcp/lazy-lions-mcp.json
- HTML version of this page: https://verifymcp.io/servers/web3kaneco-lazy-lions-mcp/lazy-lions-mcp