mcpbeat

Lightyear CryptoPunks MCP Server

io.github.Lightyear-Technologies-Limited/cryptopunks
not responding

Lightyear CryptoPunks is listed as active in the registry but did not answer our last check. It exposes 11 tools.

Browse traits, filter 10K punks, listings, bids, Merkle roots, and bid pricing for CryptoPunks.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
69.6%
Uptime 24h
64 of 92 checks
11
Tools
read from the server
313 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add cryptopunks --transport http https://punks.lightyear.build/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cryptopunks": {
      "url": "https://punks.lightyear.build/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cryptopunks]
url = "https://punks.lightyear.build/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cryptopunks": {
      "url": "https://punks.lightyear.build/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cryptopunks": {
      "url": "https://punks.lightyear.build/api/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

bids
get_bids_for_merkle_root
Get pending EIP-712 bids matching a specific Merkle root. Useful for seeing competition on a trait-based bid set. Rate limit: 10 per 10 min (read bucket — shared with browse_types, browse_traits, get_punk_details, get_listings, get_floor_price, get_bids_for_punk).
get_bids_for_punk
Get pending EIP-712 bids that include a specific CryptoPunk. Returns bids from the CryptoPunks Bids API. Rate limit: 10 per 10 min (read bucket — shared with browse_types, browse_traits, get_punk_details, get_listings, get_floor_price, get_bids_for_merkle_root).
browse
browse_traits
List all CryptoPunk traits with their counts. Optionally filter by type to see how many punks of that type have each trait. Rate limit: 10 per 10 min (read bucket — shared with browse_types, get_punk_details, get_listings, get_floor_price, get_bids_for_punk, get_bids_for_merkle_root).
browse_types
List all CryptoPunk type categories with their counts. Rate limit: 10 per 10 min (read bucket — shared with browse_traits, get_punk_details, get_listings, get_floor_price, get_bids_for_punk, get_bids_for_merkle_root).
bid
get_bid_recommendation
Analyze market data and recommend a bid price range for a CryptoPunk trait selection. Combines floor price, competing bids, and set composition into actionable guidance. `composition` lists only the traits that define the selection; use `absentTraits` for a full exclusion list when needed. Rate limit: 1 per 1 min (recommend bucket).
compute
compute_merkle_root
Compute the Merkle root for a set of CryptoPunk IDs. The root matches the on-chain Solady MerkleProofLib encoding used by the Stash contract. Rate limit: 5 per 10 min (compute bucket — shared with filter_punks, resolve_merkle_root).
filter
filter_punks
Filter CryptoPunks by type and traits. Returns matching punk IDs and their Merkle root. Rate limit: 5 per 10 min (compute bucket — shared with compute_merkle_root, resolve_merkle_root).
floor
get_floor_price
Get the current floor ask price from the native CryptoPunks marketplace. Excludes restricted (onlySellTo) and zero-value listings. Returns `totalActive` (same denominator as get_listings). Rate limit: 10 per 10 min (read bucket — shared with browse_types, browse_traits, get_punk_details, get_listings, get_bids_for_punk, get_bids_for_merkle_root).
listings
get_listings
Get currently listed CryptoPunks from the native marketplace. By default returns only publicly buyable listings (excludes restricted onlySellTo and zero-value entries); pass `includeRestricted: true` to include private bundle sales. Optionally filter by price range. Returns `totalActive` (publicly buyable listings, same denominator as get_floor_price) and `matchedCount` (after your filters). Rate limit: 10 per 10 min (read bucket — shared with browse_types, browse_traits, get_punk_details, get_floor_price, get_bids_for_punk, get_bids_for_merkle_root).
punk
get_punk_details
Get metadata for specific CryptoPunks: type, traits with rarity percentages, and permalink. Rate limit: 10 per 10 min (read bucket — shared with browse_types, browse_traits, get_listings, get_floor_price, get_bids_for_punk, get_bids_for_merkle_root).
resolve
resolve_merkle_root
Reverse-engineer a Merkle root back to its punk IDs and inferred trait selection. ONLY works for roots that already have at least one bid in the CryptoPunks Bids API — this tool looks bids up by root, then derives trait config from the resulting punk set. Returns `resolved: false` for unknown roots; constructing a root locally and passing it here will not work. Rate limit: 5 per 10 min (compute bucket — shared with filter_punks, compute_merkle_root).

Endpoints

URLTransportStateLatencyChecked
https://punks.lightyear.build/api/mcp streamable-http answering 98 ms 0 min ago

Lightyear CryptoPunks — questions

Answers built from our own checks of this server.

What can Lightyear CryptoPunks do?
It exposes 11 tools, read directly from the server on our last check. Among them: browse_traits, browse_types, compute_merkle_root, filter_punks, get_bid_recommendation, get_bids_for_merkle_root and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Lightyear CryptoPunks mostly used for?
Its tools cluster around browse and bids. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Lightyear CryptoPunks working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 64 of 92 checks got a reply (69.6%), average response time 313 ms. The bar chart above shows every period we have measured.
The registry lists Lightyear CryptoPunks as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Lightyear CryptoPunks?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lightyear CryptoPunks need an API key?
No. Lightyear CryptoPunks completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Lightyear CryptoPunks?
It answers our handshake in 313 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.