io.github.Web3kaneco/lazy-lions-mcp
NPM · LAZY-LIONS-MCP · SCANNED SEP 20
Read the Lazy Lions NFT ecosystem: tokens, traits, rarity, holders, and the $LAZY economy.
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 & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 30 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1450 tokens (~80/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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 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.
npm · lazy-lions-mcp
claude mcp add web3kaneco-lazy-lions-mcp -- npx -y lazy-lions-mcp
{
"mcpServers": {
"web3kaneco-lazy-lions-mcp": {
"command": "npx",
"args": [
"-y",
"lazy-lions-mcp"
]
}
}
} {
"servers": {
"web3kaneco-lazy-lions-mcp": {
"command": "npx",
"args": [
"-y",
"lazy-lions-mcp"
]
}
}
} codex mcp add web3kaneco-lazy-lions-mcp -- npx -y lazy-lions-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"web3kaneco-lazy-lions-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"lazy-lions-mcp"
],
"enabled": true
}
}
} openclaw mcp add web3kaneco-lazy-lions-mcp --command npx --arg -y --arg lazy-lions-mcp
mcp_servers:
web3kaneco-lazy-lions-mcp:
command: "npx"
args: ["-y", "lazy-lions-mcp"] {
"McpServers": {
"web3kaneco-lazy-lions-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"lazy-lions-mcp"
]
}
}
} assistant mcp add web3kaneco-lazy-lions-mcp -t stdio -c npx -a -y lazy-lions-mcp
{
"mcpServers": {
"web3kaneco-lazy-lions-mcp": {
"command": "npx",
"args": [
"-y",
"lazy-lions-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.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 6 Sept 26 +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.
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 20 Sept 2026 · Analysed npm/lazy-lions-mcp@1.0.1
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_collection_stats ~55
Headline stats for the ecosystem: supply, unique holders, listed counts, and unlock totals.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
No output schema declared.
No examples provided.
get_floors ~50
Current floor price for a collection, plus the cheapest listed token.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
No output schema declared.
No examples provided.
get_holder ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (0x...) or Lazy Lions username. |
| include_linked | boolean | – | Aggregate across the holder's linked wallets. |
No output schema declared.
No examples provided.
get_holder_profile ~47
Public profile for a holder: username, bio, avatar, holdings summary, and earned Pride Mark badges.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (0x...) or Lazy Lions username. |
No output schema declared.
No examples provided.
get_lazy_balance ~61
A wallet's $LAZY position: liquid balance plus any amount locked on-chain, optionally aggregated across the holder's linked wallets.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (0x...). |
| include_linked | boolean | – | Aggregate across linked wallets. |
No output schema declared.
No examples provided.
get_lazy_burns ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_lazy_leaderboard ~72
$LAZY leaderboards: wallets ranked by total tokens burned, or by amount currently locked on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: return just this wallet's rank and totals. |
| board | string | – | Which leaderboard to read. |
| limit | integer | – | How many wallets to return. |
No output schema declared.
No examples provided.
get_lazy_market ~30
Live $LAZY market data on Base: price, 24h change, volume, and liquidity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_lazy_protocol ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leaderboard ~47
Top holders ranked by total NFTs, Lions, Cubs, or badges earned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many holders to return. |
| sort_by | string | – | Ranking metric. |
No output schema declared.
No examples provided.
get_listings ~71
Tokens currently listed for sale, with prices and marketplace links.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
| limit | integer | – | Results per page (max 100). |
| offset | integer | – | Pagination offset. |
No output schema declared.
No examples provided.
get_rarity ~70
Rarity scores and ranks for a token, blending trait rarity with market signals (last sale, current ask).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
| token_id | integer | yes | On-chain token number. |
No output schema declared.
No examples provided.
get_recent_changes ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | ISO timestamp to read changes from. |
| types | string | – | Comma-separated filter, e.g. 'reroll,transfer'. |
No output schema declared.
No examples provided.
get_token ~88
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).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
| token_id | integer | yes | On-chain token number, e.g. 1922. |
No output schema declared.
No examples provided.
get_token_history ~98
History for one token: ownership transfers, and for Cubs the full reroll history showing how its art and traits changed over time.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | On-chain token number. |
No output schema declared.
No examples provided.
get_traits ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
No output schema declared.
No examples provided.
search_tokens ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
smart_search ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Which collection to query. 'lions' = Lazy Lions, 'cubs' = Lazy Cubs. |
| query | string | yes | Natural-language description of the tokens to find. |
No output schema declared.
No examples provided.
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.