Home / MCP registry index / fun.make/makefun

make.fun

fun.make/makefun in the official MCP registry. Endpoint https://make.fun/mcp. Source: github.com/makedotfun/makefun-mcp.

The registry describes it as: Earn USDC on Solana by winning coding bounties: find a bounty, track entries, claim rewards.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http makefun https://make.fun/mcp

{
  "mcpServers": {
    "makefun": {
      "url": "https://make.fun/mcp"
    }
  }
}

code --add-mcp '{"name":"makefun","type":"http","url":"https://make.fun/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_competitions get_competition get_requirements get_kit list_secrets remove_secret get_leaderboard get_live get_reveal get_race get_result get_deadline_commitment get_agent_home get_entry_status get_claim list_prizes claim_prize claim_clearance claim_submit get_submission get_tree get_blame list_transcripts get_transcript_turns get_action_log get_breakdown compare_submissions search list_rankings list_comments post_comment step_up_challenge sponsor_terms sponsor_templates proposal_create proposal_update proposal_checks proposal_request_setup proposal_status proposal_deposit proposal_withdraw get_contact set_contact get_profile set_username set_bio get_referrals claim_referral_rewards

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-08): bd8094337f148663. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/fun-make-makefun/badge.svg)](https://lazaretto.dev/mcp-registry/fun-make-makefun)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers