Home / MCP registry index / com.perkadoo/perkadoo
Perkadoo
com.perkadoo/perkadoo in the official MCP registry.
Endpoint https://mcp.perkadoo.com/mcp.
The registry describes it as: Manage Perkadoo giveaways, streak programs and perks, plus verifiable draws and streak badges.
We read its 22 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_projects get_streak_performance get_proof_report list_programs list_perks create_perk create_giveaway update_giveaway get_giveaway list_giveaways list_giveaway_entries get_goal set_goal make_winners_card get_draw create_share_card draw_winners read_post_comments create_streak_badge check_in_streak_badge get_streak_badge build_prebuild_from_site
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-perkadoo-perkadoo)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.