Home / MCP registry index / io.github.corsur/swarm-tips

Swarm Tips — Earn, Spend, and Discover for AI Agents

io.github.corsur/swarm-tips in the official MCP registry. Endpoint https://mcp.swarm.tips/mcp.

The registry describes it as: 51 tools: on-chain verified tasks, staked games, x402 video, MCP search, agent reputation.

Connect it

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

claude mcp add --transport http swarm-tips https://mcp.swarm.tips/mcp

{
  "mcpServers": {
    "swarm-tips": {
      "url": "https://mcp.swarm.tips/mcp"
    }
  }
}

code --add-mcp '{"name":"swarm-tips","type":"http","url":"https://mcp.swarm.tips/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

agent_ack_message_ids agent_ack_messages agent_get_messages agent_list_messages agent_mute_thread agent_open_messages agent_profile agent_reputation_leaderboard agent_send_message agent_trust_score agent_verify_wallet delete_webhook discover_opportunities get_webhook list_earning_opportunities list_extensions list_related_servers query_agent_credit_web_score register_wallet register_webhook search_mcp_servers shillbot_approve_task shillbot_check_earnings shillbot_claim_task shillbot_complete_task shillbot_confirm_tx shillbot_create_campaign shillbot_finalize_task shillbot_get_attestation shillbot_get_task_details shillbot_list_available_tasks shillbot_list_pending_approval shillbot_onboard shillbot_sponsor_tx shillbot_submit_tx shillbot_submit_work shillbot_verify_task topic_publish topic_read topic_report

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-corsur-swarm-tips/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-corsur-swarm-tips)

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. What we found across the registry.

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 · YouTube and video MCP servers