Block402 vs NFT Metadata API
A side-by-side look at the Block402 and NFT Metadata API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
Block402Finance & FintechBitcoin + Ethereum RPC for AI agents. 44 tools. x402 payments in USDC on Base mainnet.37FairAuth: not declaredVerdict: choose Block402 for finance & fintech work; choose NFT Metadata API for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose Block402 when
- You need dedicated capabilities in the Finance & Fintech domain.
Choose NFT Metadata API when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
crypto_get_nft_metadata, contract, tokenId.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Block402 | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 37/100 · Fair | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Block402 | View NFT Metadata API |
Tools & capabilities
Block402 tools
No tool names declared yet. Check the project README from the listing page.
NFT Metadata API tools 4
crypto_get_nft_metadataFetch NFT metadata from contract and token IDcontractNFT contract address (e.g. 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D)tokenIdToken ID within the contractchainBlockchain: 'ethereum' or 'base' (default: ethereum)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Block402
No confirmed install command for Block402 yet — follow the setup steps linked from its listing page rather than a guessed package name.
NFT Metadata API
{
"mcpServers": {
"nft-metadata-api": {
"url": "https://nft-metadata.api.klymax402.com/mcp"
}
}
}
Frequently asked questions
Block402 is categorized under Finance & Fintech and uses an install path we have not confirmed yet. NFT Metadata API belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Block402 for finance & fintech work and NFT Metadata API for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Block402 has no confirmed install command yet — follow its own setup instructions.
Block402 is listed as a paid service. NFT Metadata API has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add block402 and nft-metadata-api as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Block402 has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. NFT Metadata API has 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.