ListDrop MCP server
Which servers in the official MCP registry are ListDrop's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameco.listdrop/listdropverified in the MCP registry
The registry name sits under listdrop.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools4
- Server calls itselflistdrop
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 41 ms.
create_listSaves 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…
get_listReturns 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.
my_listsReturns 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.
send_feedbackSends 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"listdrop": {
"type": "http",
"url": "https://www.listdrop.co/mcp"
}
}
}OpenAPI spec
13 paths, read 2026-10-13. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.