co.listdrop/listdrop

name:co.listdrop/listdrop

Save list-shaped answers as lists your user can keep, share, and check off. Keyless or OAuth.

transport:: remote
credential class:: self-provisionable

Owner verification

Not yet verified. Verifying proves you control this server and is free, permanently — it never changes a published score.

Start verification →

Tools

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.
shallow
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.
shallow
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.
shallow
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.
shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/099727e9-6877-492b-aeed-7ce2c124db1c/badge.svg)](https://vouch.tools/servers/099727e9-6877-492b-aeed-7ce2c124db1c)