
Lazy Lions Mcp
io.github.Web3kanecoPublished by GitHub account Web3kanecov1.0.1Updated Oct 24, 2026
Read the Lazy Lions NFT ecosystem: tokens, traits, rarity, holders, and the $LAZY economy.
Overview
A local MCP server that lets an assistant read Lazy Lions NFT data: tokens, traits, rarity, holders and the $LAZY economy.
- What you can do
- Read Lazy Lions NFT ecosystem data through the Lazy Lions Agent API, covering tokens, traits, rarity, holders and the $LAZY economy. No individual tools are listed in the manifest, so the exact operations are not documented here. Configuration is limited to the API base URL and a request timeout.
- When to use it
- Useful when you want an assistant to look up Lazy Lions NFT details, trait and rarity information, holder data or $LAZY economy figures without leaving the chat.
- Requirements
- Runs as a local process via the npm package lazy-lions-mcp over stdio, so Node.js is needed. Network access to the Lazy Lions Agent API is required; the base URL defaults to the project's agent endpoint and can be overridden with LAZY_LIONS_API_BASE. Request timeout is set with LAZY_LIONS_TIMEOUT_MS (default 15000). No authentication is declared.
Installation
In SourceWeft
- Open Lazy Lions Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.