Official MCP RegistryListed
ListDrop
Save list-shaped answers as lists your user can keep, share, and check off. Keyless or OAuth.
First seen 2 Oct 2026. Evidence as of 2 Oct 2026.
4
Tools
From an anonymous probe
1
Source listings
Each with its own history
0
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| create_list | Saves list-shaped content as a ListDrop list the user can keep, check off, and share: an itinerary, a reading or watch list, a packing list, gift ideas, an apartment or job-search shortlist, a step-by-step plan, a checklist. Applies when the user wants a list to outlive the conversation. Not meant for throwaway answers, secrets or sensitive data (a list is unowned until claimed), or content that isn't list-shaped. Without a connected account the list is created private and unowned, and the result contains a secret claim URL: opening it is the only way to view and keep the list, and unclaimed lists are deleted after 30 days. With a connected ListDrop account (OAuth, lists:write) the list is created directly in that account, private, and the result contains its URL instead. A URL inside an item becomes a titled, linked item. Optional fields: allowed_emails shares the private list view-only with specific people, who open the returned share URL and verify their address with a one-time email link (no account needed); expires_in_days makes the list archive itself on a date, for trips and events. | Changes data |
| get_list | Returns a PUBLIC ListDrop list as markdown (title, items, notes, links), given its URL (https://www.listdrop.co/l/<id>/…) or bare id. Private lists are never readable. | Read-only |
| my_lists | Returns the connected user's own lists (titles, visibility, item counts, URLs), private ones included. Requires a connected ListDrop account (OAuth, lists:read scope); without one the server answers 401. | Read-only |
| send_feedback | Sends a message to the ListDrop team when the user asks to report a problem, request a feature, or give feedback about ListDrop. A person reads every message. No account needed. The message should contain only what the user wants sent: no claim URLs, tokens, or personal data. The email field is for a user who asked for a reply and gave their address. | Changes data |
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | co.listdrop/listdrop | 2 Oct 2026 | 2 Oct 2026 | 1 |