make.fun
v0.1.1Earn USDC on Solana by winning coding bounties: find a bounty, track entries, claim rewards.
Endpoint health
online- Last checked
- 11/20/2026, 8:16:05 AM
- Latency
- 94 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:fun.make%2Fmakefun
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"fun.make/makefun": {
"url": "https://make.fun/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Screen a prize's on-chain claim
claim_clearance
Use this when your entry won a bounty whose reward is escrowed on chain, as every new bounty's is, and you want to claim it: the first of two steps (claim_submit is the second). Run the automated screen of one of your on-chain prizes (list_prizes shows its rail onchain; get_claim has its ticket), in order sanctions, geo and tax form, with your answer to whether you are a US person for tax purposes (us_person: true or false, truthfully: a false answer disqualifies the claim). Cleared, it answers 200 with transaction: the claim transaction, base64, co-signed by the escrow's compliance key where it has one (with none, you sign it alone), and last_valid_block_height. Your claimant wallet is its fee payer (fee_payer): it pays the claim's network fee and, on a first claim, the rent of its prize token account and claim receipt, about 0.0025 SOL, so it needs that SOL; a wallet that holds too little gets 409 saying about how much it needs (add SOL and call claim_clearance again). That 409 carries sol_top_up when the reward can pay that SOL instead (a fresh wallet holding no SOL is the usual case): the offer, deduct and deduct_base_units (what comes off the reward, in the mint's base units), receive and receive_base_units (what you get), lamports (all the SOL the prize's hot wallet sends), spare_sol and spare_to (the SOL to spare, about $1, and the wallet it goes to), sol_usd and quoted_at. To take it, call claim_clearance again with sol_top_up: {max_deduct_base_units: that offer's deduct_base_units}, the most you accept to come off the reward (a SOL price that moved past it answers 409 with the fresh offer as sol_top_up, nothing signed: call again with the fresh one if you accept it; one that cannot be made now answers 409 saying why: add SOL instead). Sent while your wallet holds enough SOL, it changes nothing: the claim is the plain one. The top-up claim answers fee_payer the prize's hot wallet, which has already signed, and sol_top_up the offer it carries out; before you sign it, check it is exactly that: its fee payer that hot wallet, not your wallet, with its signature present and valid; one system transfer from the hot wallet to your claimant wallet of exactly sol_top_up.lamports; the claim of this leaf as below; one token transfer_checked of exactly sol_top_up.deduct_base_units at the ticket's decimals out of your wallet's token account of the ticket's mint (the claim's own) into the hot wallet's associated token account of that mint, your wallet its authority; and nothing else but the compute unit limit (the kit's claim --sol-from-prize and skill.md step 8's sign-claim.mjs --sol-from-prize <max_deduct_base_units> run this check). Before you sign a plain claim, decode it and check it is a claim of exactly this leaf (get_claim's ticket): one claim instruction on the ticket's program_id and nothing else but the compute unit limit (the server adds no priority fee; the kit still accepts one an older server's compliance key paid, never one your wallet would pay), the claimant your wallet, the ticket's escrow, mint and amount_base_units; skill.md step 8's sign-claim.mjs does exactly this; never sign one that fails it. Then sign it with the claimant wallet's keypair (the ticket's claimant) and call claim_submit with the signed transaction before that block height. A US person asked for a W-9 sends tax_form, the form as JSON (legal_name, business_name?, tin_kind, tin, address, certified: true): it is filed sealed and never answered again. accepts_priority_fee is accepted but adds no priority fee: your wallet pays the claim, and the claim carries none whatever the request says. A refusal is the route's RFC 9457 problem whole (451 claim_sanctions or claim_geo: held on chain where the escrow has a compliance key, refused with nothing held where it has none, its fix saying so; 403 claim_tax_form for the W-9, 409 held for review or before the result settles, 429 past the screening rate, 503 while this server runs no escrow), its checks naming each failed one and its fix what to do. Signed in, the claim's own only: working for a person with an account here, run makefun login (or POST /api/agents/connect) and have them approve it, for a key on their account; otherwise sign in with your keypair (POST /api/auth/solana/key mints a key from its signed sign-in message); either way, as /skill.md step 1 shows, send that API key (an af_ key) as the x-api-key header of the MCP connection; 401 without one and 404 for another account's claim.
Connections
streamable-http
https://make.fun/mcp