Skip to content

ListDrop MCP server

co.listdrop/listdroplistdrop.costreamable-httpv1.0.0Scanned

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

4 tools: 1 do something that can't be undone, 1 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 1 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ListDrop MCP server can do

The ListDrop MCP server is published by listdrop.co, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (1 tool: create_list), but cannot delete data. 2 tools only read.

1 tool reads private data (get_list); 2 tools bring in text other people can write (create_list and get_list); 1 tool can send data out of your system (send_feedback). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 1Claude Code: ask
  • send_feedbackSends a message to the ListDrop team when the user asks to report a problem, request a feature, or give feedback about ListDrop.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send feedback to the ListDrop team
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 1Claude Code: ask
  • 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "create_list" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Save a list to ListDrop
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_listReturns a PUBLIC ListDrop list as markdown (title, items, notes, links), given its URL (https://www.listdrop.co/l/<id>/…) or bare id.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_list" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read a public ListDrop list
    • readOnlyHint: true
    • openWorldHint: false
  • my_listsReturns the connected user's own lists (titles, visibility, item counts, URLs), private ones included.No findings

    Why it is in this group

    • The name "my_lists" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List the user's ListDrop lists
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__listdrop__send_feedback"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.listdrop.co/.well-known/oauth-protected-resource/mcp
Authorization servers
https://www.listdrop.co
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.listdrop.co/mcp: tools/list returned 4 tools to an anonymous client, including send_feedback (irreversible), create_list (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http listdrop https://www.listdrop.co/mcp
claude mcp add --transport http listdrop https://www.listdrop.co/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__listdrop__get_list",
      "mcp__listdrop__my_lists"
    ],
    "ask": [
      "mcp__listdrop__create_list",
      "mcp__listdrop__send_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as listdrop. Review it before you use it.

Capability tags behind 3 rules
  • mcp__listdrop__create_list untrusted-input
  • mcp__listdrop__get_list private-data, untrusted-input
  • mcp__listdrop__send_feedback outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.listdrop/listdrop/verify?hash=282eb57ae8546352f8abeda78ff13c2f85c8bc922ad6193eccc27276f83304d2" | jq -e '.changed == false'

Pinned hash 282eb57ae854, from Nov 12, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.listdrop/listdrop/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.listdrop/listdrop
[![Anlyon Radar](https://radar.anlyon.com/badge/co.listdrop/listdrop.svg)](https://radar.anlyon.com/servers/co.listdrop/listdrop)

Source: MCP Registry. Synced Oct 21, 2026, 17:47 UTC.

ListDrop MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ListDrop MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ListDrop MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ListDrop MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the ListDrop MCP server have?

4 tools: 1 irreversible, 1 write, 2 read. send_feedback, create_list, get_list and my_lists.

Does the ListDrop MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ListDrop MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.

Has the ListDrop MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.