Lightyear CryptoPunks
REMOTE · PUNKS.LIGHTYEAR.BUILD · SCANNED SEP 20
Browse traits, filter 10K punks, listings, bids, Merkle roots, and bid pricing for CryptoPunks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1277 tokens (~116/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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 Lightyear CryptoPunks MCP server?
Lightyear CryptoPunks is a hosted endpoint at https://punks.lightyear.build/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · punks.lightyear.build
claude mcp add --transport http lightyear-technologies-limited-cryptopunks 'https://punks.lightyear.build/api/mcp'
{
"mcpServers": {
"lightyear-technologies-limited-cryptopunks": {
"url": "https://punks.lightyear.build/api/mcp"
}
}
} {
"servers": {
"lightyear-technologies-limited-cryptopunks": {
"type": "http",
"url": "https://punks.lightyear.build/api/mcp"
}
}
} [mcp_servers.lightyear-technologies-limited-cryptopunks] url = "https://punks.lightyear.build/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lightyear-technologies-limited-cryptopunks": {
"type": "remote",
"url": "https://punks.lightyear.build/api/mcp",
"enabled": true
}
}
} openclaw mcp add lightyear-technologies-limited-cryptopunks --url 'https://punks.lightyear.build/api/mcp' --transport streamable-http
mcp_servers:
lightyear-technologies-limited-cryptopunks:
url: "https://punks.lightyear.build/api/mcp" {
"McpServers": {
"lightyear-technologies-limited-cryptopunks": {
"Transport": "http",
"Url": "https://punks.lightyear.build/api/mcp"
}
}
} assistant mcp add lightyear-technologies-limited-cryptopunks -t streamable-http -u 'https://punks.lightyear.build/api/mcp'
{
"mcpServers": {
"lightyear-technologies-limited-cryptopunks": {
"type": "http",
"url": "https://punks.lightyear.build/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 · Probed https://punks.lightyear.build/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=punks.lightyear.build | CN=YR2,O=Let's Encrypt,C=US | 20 Jul 2026 | 18 Oct 2026 | RSA 2048 | SHA256-RSA | 5d79dc506b17e28af22bf3d5b66750cdef9 |
| SANs: punks.lightyear.build | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of punks.lightyear.build. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| build. | present | 30770, 38839 | 8, 8 | Verified |
| lightyear.build. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://plausible.io; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob:; font-src 'self' https://fonts.reown.com; connect-src 'self' https://eth-mainnet.g.alchemy.com https://*.alchemy.com https://relay.walletconnect.com wss://relay.walletconnect.com https://*.walletconnect.com https://*.walletconnect.org wss://*.walletconnect.org https://cca-lite.coinbase.com https://rpc.ankr.com https://eth.llamarpc.com https://cloudflare-eth.com https://pulse.walletconnect.org https://api.web3modal.org https://api.web3modal.com https://*.reown.com https://api.coingecko.com https://plausible.io; frame-src 'self' https://verify.walletconnect.com https://verify.walletconnect.org; worker-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://punks.lightyear.build/api/mcp | Verified | 200 | |
| http (plaintext) | http://punks.lightyear.build/api/mcp | HTTPS enforced | 308 | https://punks.lightyear.build/api/mcp |
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 →
browse_traits ~104
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).
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Filter counts to a specific type (e.g. 'Male', 'Zombie') |
No output schema declared.
No examples provided.
browse_types ~65
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compute_merkle_root ~90
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).
| Name | Type | Req | Description |
|---|---|---|---|
| punkIds | array | yes | Punk IDs to include in the Merkle tree (1-10000) |
No output schema declared.
No examples provided.
filter_punks ~126
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).
| Name | Type | Req | Description |
|---|---|---|---|
| excludedTraits | array | – | Traits to exclude |
| includedTraits | array | – | Traits to include |
| matchMode | string | – | 'all' = punk must have every included trait, 'any' = at least one |
| types | array | – | Type names to include (e.g. ['Male', 'Zombie']). Empty = all types. |
No output schema declared.
No examples provided.
get_bid_recommendation ~148
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).
| Name | Type | Req | Description |
|---|---|---|---|
| excludedTraits | array | – | Traits to exclude |
| includedTraits | array | – | Traits to include |
| matchMode | string | – | – |
| punkIds | array | – | Explicit punk IDs (overrides trait filters) |
| types | array | – | Type names to filter (e.g. ['Male', 'Zombie']) |
No output schema declared.
No examples provided.
get_bids_for_merkle_root ~116
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max bids to return (default 5) |
| merkleRoot | string | yes | Merkle root (0x-prefixed, 32 bytes hex) |
No output schema declared.
No examples provided.
get_bids_for_punk ~110
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max bids to return (default 5) |
| punkId | integer | yes | Punk ID to look up bids for |
No output schema declared.
No examples provided.
get_floor_price ~94
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_listings ~200
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).
| Name | Type | Req | Description |
|---|---|---|---|
| includeRestricted | boolean | – | Include restricted (onlySellTo) and zero-value listings. Default false — matches get_floor_price. |
| limit | integer | – | Max results (default 50) |
| maxPriceEth | number | – | Maximum price in ETH |
| minPriceEth | number | – | Minimum price in ETH |
No output schema declared.
No examples provided.
get_punk_details ~89
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).
| Name | Type | Req | Description |
|---|---|---|---|
| punkIds | array | yes | Punk IDs to look up (1-100) |
No output schema declared.
No examples provided.
resolve_merkle_root ~135
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).
| Name | Type | Req | Description |
|---|---|---|---|
| merkleRoot | string | yes | Merkle root to resolve (0x-prefixed, 32 bytes hex) |
No output schema declared.
No examples provided.
What is the Lightyear CryptoPunks MCP server?
Lightyear CryptoPunks is an MCP server listed in the public MCP registry as io.github.Lightyear-Technologies-Limited/cryptopunks. Browse traits, filter 10K punks, listings, bids, Merkle roots, and bid pricing for CryptoPunks. This page covers its hosted endpoint (https://punks.lightyear.build/api/mcp).
Is the Lightyear CryptoPunks MCP server safe to use?
Lightyear CryptoPunks scores 81 out of 100 on VerifyMCP. 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 Lightyear CryptoPunks MCP server expose?
Lightyear CryptoPunks exposes 11 tools: browse_types, browse_traits, filter_punks, get_punk_details, compute_merkle_root, and 6 more. Their descriptions and schemas cost roughly 1,277 tokens of context every time the server is loaded.
Does the Lightyear CryptoPunks MCP server require authentication?
No. We connected to Lightyear CryptoPunks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lightyear CryptoPunks MCP server still maintained?
Lightyear CryptoPunks 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.