com.mcparmory/alchemy-nft
OCI · GHCR.IO/MCPARMORY/ALCHEMY-NFT:1.0.3 · 2 COMPONENTS · SCANNED SEP 20
Retrieve NFT metadata, ownership, and contract details across blockchains
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4161 tokens (~148/item across 28 items; 28 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 Management83
- Stability observed for 25 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 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/alchemy-nft MCP server?
com.mcparmory/alchemy-nft runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/alchemy-nft:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/alchemy-nft:1.0.3
claude mcp add com-mcparmory-alchemy-nft -- docker run --rm -i ghcr.io/mcparmory/alchemy-nft:1.0.3
{
"mcpServers": {
"com-mcparmory-alchemy-nft": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/alchemy-nft:1.0.3"
]
}
}
} {
"servers": {
"com-mcparmory-alchemy-nft": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/alchemy-nft:1.0.3"
]
}
}
} codex mcp add com-mcparmory-alchemy-nft -- docker run --rm -i ghcr.io/mcparmory/alchemy-nft:1.0.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-alchemy-nft": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/alchemy-nft:1.0.3"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-alchemy-nft:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/alchemy-nft:1.0.3"] {
"McpServers": {
"com-mcparmory-alchemy-nft": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/alchemy-nft:1.0.3"
]
}
}
} {
"mcpServers": {
"com-mcparmory-alchemy-nft": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/alchemy-nft:1.0.3"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
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 oci/ghcr.io/mcparmory/alchemy-nft:1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
batch_get_contract_metadata Batch Get Contract Metadata ~97
Retrieve metadata for multiple contract addresses in a single request. Efficiently fetch contract information such as name, symbol, and decimals for a batch of addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddresses | array | – | Array of contract addresses to retrieve metadata for. Each address should be a valid Ethereum address format. If not provided, defaults to a sample set of addresses. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
batch_retrieve_nft_metadata Batch Retrieve NFT Metadata ~107
Retrieve metadata for multiple NFT contracts in a single request. Supports up to 100 tokens across Ethereum, Polygon, Arbitrum, Optimism, Base, World Chain, and other supported networks.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokens | array | yes | Array of token objects to fetch metadata for, with a maximum of 100 items per request. Each token object should specify the contract address and token ID. |
No output schema declared.
No examples provided.
calculate_nft_attribute_rarity Calculate NFT Attribute Rarity ~122
Calculates the rarity score for each attribute of a specific NFT by analyzing how uncommon each attribute is within the collection. Available on Ethereum mainnet and Polygon (mainnet and Mumbai testnet).
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection. Supports both ERC721 and ERC1155 token standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokenId | string | yes | The unique identifier of the NFT token within the contract. Can be provided in either hexadecimal or decimal format. |
No output schema declared.
No examples provided.
check_nft_airdrop Check NFT Airdrop ~133
Determines whether a specific NFT token was received as an airdrop, defined as an NFT minted to a user address in a transaction sent by a different address. Available on Ethereum mainnet and Polygon (mainnet, amoy, and mumbai).
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection. Supports both ERC721 and ERC1155 token standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokenId | string | yes | The unique identifier of the token within the contract. Can be provided in either hexadecimal or decimal format. |
No output schema declared.
No examples provided.
check_nft_holder Check NFT Holder ~117
Verify whether a wallet address holds any NFTs from a specific contract. Supports ERC721 and ERC1155 tokens across Ethereum and multiple Layer 2 networks including Polygon, Arbitrum, Optimism, and Base.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The NFT contract address to check against. Must be a valid ERC721 or ERC1155 contract. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| wallet | string | yes | The wallet address to check for NFT holdings from the specified contract. |
No output schema declared.
No examples provided.
check_spam_contract Check Spam Contract ~85
Checks whether a specific NFT contract is flagged as spam by Alchemy. This helps identify potentially fraudulent or low-quality NFT collections across supported blockchain networks.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain address of the NFT contract to check. Supports ERC721 and ERC1155 contract standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
check_token_airdrop Check Token Airdrop ~114
Determines whether an NFT token was distributed as an airdrop by checking if it was minted to a user address in a transaction sent by a different address.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain contract address for the NFT collection. Supports both ERC721 and ERC1155 token standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokenId | string | yes | The unique identifier of the token within the contract. Can be provided in either hexadecimal or decimal format. |
No output schema declared.
No examples provided.
check_wallet_nft_collection_ownership Check Wallet NFT Collection Ownership ~133
Verifies whether a specific wallet address holds at least one NFT from a given collection. Supports both ERC721 and ERC1155 token standards, and accepts wallet addresses in ENS format on Ethereum Mainnet.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection to check. Must be a valid ERC721 or ERC1155 contract address. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| wallet | string | yes | The wallet address to check for NFT ownership. Can be a standard hexadecimal address or an ENS name (Ethereum Mainnet only). |
No output schema declared.
No examples provided.
get_collection_metadata Get Collection Metadata ~99
Retrieve high-level metadata and contract information for an NFT collection using its OpenSea slug. Supported across Ethereum and multiple Layer 2 networks including Polygon, Arbitrum, Optimism, and Base.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionSlug | string | yes | The OpenSea collection slug—a URL-friendly identifier for the NFT collection (e.g., 'boredapeyachtclub'). |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
get_nft_collection_attribute_summary Get NFT Collection Attribute Summary ~106
Retrieve a summary of attribute prevalence and distribution for an NFT collection. This endpoint analyzes trait frequency across all NFTs in a contract to provide insights into attribute rarity and composition. Available on Ethereum mainnet and Polygon (mainnet and Mumbai).
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain contract address for the NFT collection to analyze. Supports both ERC721 and ERC1155 token standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
get_nft_collection_floor_prices Get NFT Collection Floor Prices ~104
Retrieves the current floor prices for an NFT collection across supported marketplaces (OpenSea and Looksrare on Ethereum mainnet). Use this to monitor pricing trends and compare floor prices across different trading platforms.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection (supports both ERC721 and ERC1155 standards). This identifies which collection's floor prices to retrieve. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
get_nft_contract_metadata Get NFT Contract Metadata ~96
Retrieve high-level metadata for an NFT contract or collection, including details about the contract itself. Supports ERC721 and ERC1155 contracts across Ethereum and multiple Layer 2 networks.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain address of the NFT contract. Must be a valid contract address for ERC721 or ERC1155 token standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
get_nft_metadata Get NFT Metadata ~156
Retrieve detailed metadata for a specific NFT by its token ID and contract address. Supports ERC721 and ERC1155 tokens across Ethereum and multiple Layer 2 networks including Polygon, Arbitrum, Optimism, and Base.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection. Must be a valid ERC721 or ERC1155 contract address. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokenId | string | yes | The unique identifier of the NFT token. Can be provided in either hexadecimal or decimal format. |
| tokenType | string | – | The token standard type: either 'ERC721' or 'ERC1155'. Specifying this improves query performance. |
No output schema declared.
No examples provided.
get_nft_owners Get NFT Owners ~127
Retrieves the current owner(s) of a specific NFT token. Supports ERC721 and ERC1155 contracts across Ethereum, Polygon, Arbitrum, Optimism, Base, World Chain, and other supported networks.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection. Must be a valid ERC721 or ERC1155 contract address. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokenId | string | yes | The unique identifier of the token within the contract. Can be provided in either hexadecimal or decimal format. |
No output schema declared.
No examples provided.
get_token_owners Get Token Owners ~144
Retrieve the owner(s) of a specific NFT token by contract address and token ID. Supports pagination to handle multiple owners.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain contract address of the NFT collection. Must be a valid Ethereum address (e.g., ERC-721 or ERC-1155 contract). |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| pageSize | integer | – | Maximum number of owner records to return per page. Use this to control response size when a token has multiple owners. |
| tokenId | string | yes | The unique identifier of the token within the contract. Accepts both hexadecimal and decimal formats. |
No output schema declared.
No examples provided.
list_nft_collection_owners List NFT Collection Owners ~115
Retrieves all wallet addresses that own NFTs from a specified ERC721 or ERC1155 contract, with optional token balance details per owner.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain contract address for the NFT collection. Supports both ERC721 and ERC1155 token standards. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| withTokenBalances | boolean | – | When enabled, includes the token balance for each token ID owned by each address. Disabled by default for faster responses. |
No output schema declared.
No examples provided.
list_nft_collections_by_owner List NFT Collections by Owner ~153
Retrieves all NFT collections owned by a specified address on Ethereum. Returns collection details with optional metadata to support portfolio analysis and collection discovery.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| owner | string | yes | The wallet address to query for NFT collections. Accepts standard Ethereum addresses or ENS names (on Ethereum Mainnet only). |
| pageSize | integer | – | Number of collections to return per page, ranging from 1 to 100. Defaults to 100 for maximum results per request. |
| withMetadata | boolean | – | Include full NFT metadata in the response when enabled. Disable to reduce payload size and improve response speed if metadata is not needed. |
No output schema declared.
No examples provided.
list_nft_contract_owners List NFT Contract Owners ~133
Retrieves all wallet addresses that own NFTs from a specific contract. Supports ERC721 and ERC1155 tokens across Ethereum and multiple Layer 2 networks including Polygon, Arbitrum, Optimism, and Base.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The blockchain address of the NFT contract to query. Must be a valid ERC721 or ERC1155 contract address. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| withTokenBalances | boolean | – | When enabled, includes the token balance for each token ID owned by each address. Disabled by default for faster responses. |
No output schema declared.
No examples provided.
list_nft_contracts_by_owner List NFT Contracts by Owner ~257
Retrieves all NFT contracts owned by a specified address. Optionally returns detailed metadata and supports filtering by spam confidence level and custom ordering.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| orderBy | string | – | Sort contracts by transfer time (newest first) or by default contract address and token ID ordering. Transfer time ordering is supported on major networks including Ethereum, Optimism, Polygon, Base,… |
| owner | string | yes | The wallet address to query for NFT contracts. Accepts standard Ethereum addresses or ENS names (on Ethereum Mainnet). |
| pageSize | integer | – | Number of contracts to return per page, up to a maximum of 100. Defaults to 100. |
| spamConfidenceLevel | string | – | Filter out spam contracts based on confidence level. Higher confidence levels filter more aggressively (e.g., HIGH filters both HIGH and VERY_HIGH confidence spam). Defaults vary by network: VERY_HIG… |
| withMetadata | boolean | – | Include detailed NFT metadata in the response. Disabling this reduces payload size and may improve response speed. Defaults to true. |
No output schema declared.
No examples provided.
list_nft_sales List NFT Sales ~385
Retrieves NFT sales transactions that have occurred through on-chain marketplaces. Supports filtering by block range, marketplace, collection, token ID, and trade participant role. Available on Ethereum (Seaport, Wyvern, X2Y2, Blur, LooksRare, Cryptopunks), Polygon (Seaport), and Optimism (Seaport) mainnets.
| Name | Type | Req | Description |
|---|---|---|---|
| fromBlock | string | – | The starting block number for fetching NFT sales data. Accepts decimal integers, hexadecimal integers (prefixed with 0x), or 'latest'. Defaults to block 0. |
| limit | integer | – | Maximum number of NFT sales to return in the response. Accepts values up to 1000, which is also the default. |
| marketplace | string | – | Filter sales by a specific NFT marketplace. Supported values are seaport, looksrare, x2y2, wyvern, blur, and cryptopunks. Omit to return sales from all supported marketplaces. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| order | string | – | Sort order for results relative to the block range. Choose 'asc' for ascending order from the start block or 'desc' for descending order. Defaults to descending. |
| taker | string | – | Filter by the participant role in the trade. Use 'BUYER' to return sales where the specified address was the buyer, or 'SELLER' for the seller role. Omit to return both buyer and seller trades. |
| toBlock | string | – | The ending block number for fetching NFT sales data. Accepts decimal integers, hexadecimal integers (prefixed with 0x), or 'latest'. Defaults to the latest block. |
| tokenId | string | – | Filter sales to a specific NFT token ID within the collection. Omit to return sales for all token IDs in the collection. |
No output schema declared.
No examples provided.
list_nfts List NFTs ~282
Retrieves all NFTs currently owned by a specified address, with optional filtering by contract, metadata inclusion, and spam confidence levels.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddresses | array | – | Optional list of contract addresses to filter results. Specify up to 45 contract addresses to narrow the response to specific NFT collections. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| orderBy | string | – | How to order NFTs in the response. Use 'transferTime' to sort by most recent transfers first (supported on major networks). If unspecified, NFTs are ordered by contract address and token ID. |
| owner | string | yes | The wallet address to query for NFT ownership. Accepts standard Ethereum addresses or ENS names (on Ethereum Mainnet). |
| pageSize | integer | – | Number of NFTs to return per page, up to a maximum of 100. Defaults to 100. |
| spamConfidenceLevel | string | – | Filter spam NFTs by confidence level. Choose from VERY_HIGH, HIGH, MEDIUM, or LOW—any spam at that level or higher will be excluded. Defaults vary by network (VERY_HIGH for Ethereum Mainnet, MEDIUM f… |
| withMetadata | boolean | – | Whether to include full NFT metadata in the response. Set to false to reduce payload size and improve response speed; defaults to true. |
No output schema declared.
No examples provided.
list_nfts_by_owner List NFTs by Owner ~291
Retrieves all NFTs currently owned by a specified wallet address. Supports Ethereum, Polygon, Arbitrum, Optimism, Base, and other major networks with optional filtering, metadata inclusion, and custom ordering.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddresses | array | – | Optional list of NFT contract addresses to filter results. Specify up to 45 contract addresses to narrow the response to specific collections. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| orderBy | string | – | Sort NFTs in the response by transfer time (newest first) or by default contract address and token ID. Transfer time ordering is available on major networks including Ethereum, Polygon, Arbitrum, Opt… |
| owner | string | yes | The wallet address to query for NFT ownership. Accepts standard hex addresses or ENS names (Ethereum Mainnet only). |
| pageSize | integer | – | Number of NFTs to return per page, up to a maximum of 100. Defaults to 100 if not specified. |
| spamConfidenceLevel | string | – | Filter out suspected spam NFTs based on confidence level. Higher levels (VERY_HIGH, HIGH) remove more spam but may exclude legitimate tokens. Defaults vary by network and requires a paid tier. |
| withMetadata | boolean | – | Include full NFT metadata in the response. Set to false to reduce payload size and improve response speed if metadata is not needed. |
No output schema declared.
No examples provided.
list_nfts_for_collection List NFTs for Collection ~198
Retrieves all NFTs associated with a specific NFT collection across Ethereum and supported Layer 2 networks including Polygon, Arbitrum, Optimism, and Base. Supports pagination and optional metadata inclusion.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionSlug | string | – | String - OpenSea slug for the NFT collection. |
| contractAddress | string | – | String - Contract address for the NFT contract (ERC721 and ERC1155 supported). |
| limit | integer | – | Maximum number of NFTs to return per request. Defaults to 100. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| startToken | string | – | Token ID offset for pagination, specified as either a hexadecimal or decimal string. Use this to resume from a previous position or fetch multiple token ranges in parallel. |
| withMetadata | boolean | – | When true, includes full NFT metadata in the response; when false, reduces payload size for faster queries. Defaults to true. |
No output schema declared.
No examples provided.
list_nfts_for_contract List NFTs for Contract ~191
Retrieves all NFTs associated with a specific NFT contract address. Supports ERC721 and ERC1155 standards across Ethereum and multiple Layer 2 networks including Polygon, Arbitrum, Optimism, and Base.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection. Must be a valid ERC721 or ERC1155 contract address. |
| limit | integer | – | Maximum number of NFTs to return per request. Defaults to 100 if not specified. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| startToken | string | – | Token ID offset for pagination, allowing you to start from a specific position or fetch multiple token ranges in parallel. Accepts hexadecimal or decimal format. |
| withMetadata | boolean | – | Whether to include full NFT metadata in the response. Set to false to reduce payload size and improve response speed if metadata is not needed. |
No output schema declared.
No examples provided.
list_spam_contracts List Spam Contracts ~75
Retrieve a list of all spam contracts identified and marked by Alchemy. This endpoint is available only on paid tier accounts and supports multiple blockchain networks including Ethereum, Polygon, Arbitrum, Optimism, Base, and others.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
refresh_nft_metadata Refresh NFT Metadata ~138
Submits a request to refresh the cached metadata for a specific NFT token. Supported on Ethereum (Mainnet & Sepolia), Polygon (Mainnet, Mumbai & Amoy), Arbitrum One, Optimism, and Base mainnets.
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract address of the NFT collection containing the token you want to refresh. Must be a valid Ethereum-format address. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| tokenId | string | yes | The unique token ID within the specified contract that you want to refresh. Must correspond to an existing token in the contract. |
No output schema declared.
No examples provided.
report_spam_address Report Spam Address ~122
Report a blockchain address as spam to help protect the network. This operation flags addresses suspected of malicious activity on supported chains including Ethereum, Polygon, Base, Arbitrum, Optimism, and others.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The blockchain address to report, provided as a hexadecimal string (e.g., starting with 0x). |
| isSpam | boolean | yes | Set to true to mark the address as spam, or false to remove a previous spam report. |
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
No output schema declared.
No examples provided.
search_contract_metadata Search Contract Metadata ~81
Search for keywords across metadata of ERC-721 and ERC-1155 smart contracts. Currently available on Ethereum, Polygon, Arbitrum, Optimism, and Base networks.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Target blockchain network. Determines which chain to query for NFT data. |
| query | string | yes | The search keyword or phrase to find within contract metadata fields. |
No output schema declared.
No examples provided.
What is the com.mcparmory/alchemy-nft MCP server?
com.mcparmory/alchemy-nft is an MCP server listed in the public MCP registry as com.mcparmory/alchemy-nft. Retrieve NFT metadata, ownership, and contract details across blockchains. This page covers its container image (ghcr.io/mcparmory/alchemy-nft:1.0.3).
Is the com.mcparmory/alchemy-nft MCP server safe to use?
com.mcparmory/alchemy-nft scores 49 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 com.mcparmory/alchemy-nft MCP server expose?
com.mcparmory/alchemy-nft exposes 28 tools: list_nfts_by_owner, list_nfts_for_contract, list_nfts_for_collection, get_nft_metadata, batch_retrieve_nft_metadata, and 23 more. Their descriptions and schemas cost roughly 4,161 tokens of context every time the server is loaded.
Is the com.mcparmory/alchemy-nft MCP server still maintained?
com.mcparmory/alchemy-nft 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.