Skip to content
External endpointresponds

Grabblist

Save and organize web finds in persistent, user-controlled collections for AI assistants.

Endpoint URL
https://mcp.grabbitapp.com/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
266 ms
Response record
1 of 1 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.grabbitapp/grabblist

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Grabblist
Version
2.1.0
Capability keys
tools
Tool names
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, ask_agent
Instructions excerpt

Grabblist is a personal Grabblist for things you find online — products, services, rentals, courses, listings — anything with a title, price, and URL. Each saved item is a static snapshot of info at save time. Data does not auto-update. Terminology: each record is an "item", the collection of items is a "Grabblist" or "saved items". Item types: product, rental, service, course, listing, event, other. Detect from context — a hotel is "rental", an online class is "course", a Facebook listing is "listing", a concert ticket is "event". Items have a source field (extension, mcp, manual) and a decision status flow: considering → shortlisted → decided → bought | rejected. Items can have a target_price (what the user wants to pay) and can be linked with relations: alternative, complement, upgrade, duplicate, same_seller. Collections are folders for organizing items. They can have a budget. Deleting a collection does not delete items inside. All mutation tools accept an option

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 266ms