Skip to content
ListDrop logo

ListDrop

Turns pasted chatbot answers and shared lists into followable, forkable checklists, reachable through an MCP server or keyless API.

At a glanceswept 2026-10-12

not read yet

Use

For
People who want to save, share and follow lists, including answers copied from ChatGPT or Claude.
Price
Price not read
Activity
Actively maintainedsite updated 2 weeks ago
Company
founding year not on record
Runs as
API
What people do with it
  • save a chatbot answer as a checkable list
  • follow a friend's list and receive its updates
  • fork someone else's list and tick off your own copy
The companyeach fact with its source · read 2026-10-12
  • HeadquartersBenito Juárez, MXper their site
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverco.listdrop/listdropverified in the MCP registry
  • Stateanswers, 4 toolschecked 2026-10-13
  • Address to connectwww.listdrop.co/mcp
  • OpenAPI spec13 pathsthe spec ↗

MCP server details →

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.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Agents tools →

Questions this page answers
  • What is ListDrop?

    Turns pasted chatbot answers and shared lists into followable, forkable checklists, reachable through an MCP server or keyless API. It is listed in the Atlas under Agents.

  • Who is ListDrop for?

    People who want to save, share and follow lists, including answers copied from ChatGPT or Claude.

  • Do people use ListDrop?

    Little sign of use.

  • Is ListDrop still maintained?

    Actively maintained: site updated 2 weeks ago.

  • What are alternatives to ListDrop?

    In Agents, by use: Hoaster, AgentTune, PromptsForEveryone.com, Dijin, Cloudflare, Claude.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.