Home / MCP registry index / com.gotcashback/gotcashback
GotCashback
com.gotcashback/gotcashback in the official MCP registry.
Endpoint https://mcp.gotcashback.com/.
The registry describes it as: Compare cashback rates from 100+ portals in 40+ countries and find discounted gift cards.
We read its 18 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
get_portals get_cashback_rates_by_store_id get_countries get_gift_cards_by_store_id get_portals_by_name get_stores_by_country get_my_alerts get_gift_cards_by_store_name get_my_profile get_stores_by_name get_portal_by_id get_cashback_rates_by_store_name set_store_alert toggle_favorite_store get_my_favorite_stores remove_store_alert get_best_deals_by_brand get_best_deals_by_category
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-gotcashback-gotcashback)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.