Home / MCP registry index / com.grabbitapp/grabblist
Grabblist
com.grabbitapp/grabblist in the official MCP registry.
Endpoint https://mcp.grabbitapp.com/api/mcp.
The registry describes it as: Save and organize web finds in persistent, user-controlled collections for AI assistants.
We read its 22 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
ping get_wishlist get_item add_item delete_item restore_item search_saved update_price update_item list_collections create_collection add_to_collection remove_from_collection delete_collection update_collection link_items get_item_graph unlink_items get_item_history get_collection_activity set_pinned_items send_feedback
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-grabbitapp-grabblist)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.