Airdrop Checker API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Check wallet eligibility for active crypto airdrops — LayerZero, EigenLayer, Scroll. x402.

VerifiedSSEWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Remote MCP endpoint that checks an Ethereum wallet address for eligibility in active crypto airdrops and returns estimated values and claim links.

What you can do
Check a wallet address for airdrop eligibility, returning eligible airdrops, total count, estimated USD value, claim URLs and deadlines via the crypto_check_airdrops tool (GET and POST variants).
When to use it
Useful when you want an assistant to look up unclaimed airdrops for one or more Ethereum wallets, or to feed eligibility results into a monitoring or dashboard workflow.
Requirements
A remote MCP endpoint reached over SSE; no API key or signup. Each call is paid per request in USDC on Base L2 through the x402 protocol, so an x402-capable client with a funded wallet is needed.
Before you install
Every call costs money ($0.012 per check in USDC on Base), so repeated or bulk checks spend funds. The wallet address you submit is sent to a third-party service, and results are estimates from that provider, not authoritative claim data.

Installation

In SourceWeft

  1. Open Airdrop Checker API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fairdrop-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "airdrop-checker-api": {
      "type": "sse",
      "url": "https://airdrop-checker.api.klymax402.com/mcp"
    }
  }
}

README

Airdrop Checker API

[MCP Server] [x402] [License: MIT]

Check wallet eligibility for active crypto airdrops -- token, value, deadline, claim URL via Etherscan. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "airdrop-checker": {      "url": "https://airdrop-checker.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl "https://airdrop-checker.api.klymax402.com/api/check?address=0x0000000000000000000000000000000000dEaD"# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
crypto_check_airdropsGET/api/check$0.012Check wallet eligibility for crypto airdrops
crypto_check_airdropsPOST/api/check$0.012Check wallet eligibility for crypto airdrops (POST variant)

crypto_check_airdrops

Use this when you need to check if a wallet address is eligible for crypto airdrops. Scans wallet interactions against known airdrop contracts and returns eligible claims.

Parameters

NameTypeRequiredDescription
addressstringyesEthereum wallet address (0x...)

Returns

  • eligible -- array of airdrops the wallet qualifies for
  • totalEligible -- number of eligible airdrops found
  • totalEstimatedValue -- combined estimated USD value of all eligible airdrops
  • walletAddress -- the address checked
  • checkedAt -- timestamp of the check

Example response:

json
{"eligible":[{"tokenName":"LayerZero","tokenSymbol":"ZRO","estimatedValueUsd":450,"deadline":"2026-06-30T00:00:00Z","claimUrl":"https://claim.layerzero.network","status":"claimable"}],"totalEligible":3,"totalEstimatedValue":1250,"walletAddress":"0x742d...","checkedAt":"2026-04-13T12:00:00Z"}

When to use: discovering unclaimed airdrops, monitoring multiple wallets for eligibility, or building airdrop farming dashboards.

crypto_check_airdrops

Use this when you need to check if a wallet address is eligible for crypto airdrops. Scans wallet interactions against known airdrop contracts and returns eligible claims. POST variant of crypto_check_airdrops -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
addressstringyesEthereum wallet address (0x...)

Returns

  • eligible -- array of airdrops the wallet qualifies for
  • totalEligible -- number of eligible airdrops found
  • totalEstimatedValue -- combined estimated USD value of all eligible airdrops
  • walletAddress -- the address checked
  • checkedAt -- timestamp of the check

Example response:

json
{"eligible":[{"tokenName":"LayerZero","tokenSymbol":"ZRO","estimatedValueUsd":450,"deadline":"2026-06-30T00:00:00Z","claimUrl":"https://claim.layerzero.network","status":"claimable"}],"totalEligible":3,"totalEstimatedValue":1250,"walletAddress":"0x742d...","checkedAt":"2026-04-13T12:00:00Z"}

When to use: discovering unclaimed airdrops, monitoring multiple wallets for eligibility, or building airdrop farming dashboards.

Example agent prompts

  • "Check if a wallet address is eligible for crypto airdrops"
  • "Check if a wallet address is eligible for crypto airdrops"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit 3594abb

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% 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 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 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
  • License10 pts