ListDrop
REMOTE · WWW.LISTDROP.CO · SCANNED OCT 4
Save list-shaped answers as lists your user can keep, share, and check off. Keyless or OAuth.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 576 tokens (~144/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ListDrop MCP server?
ListDrop is a hosted endpoint at https://www.listdrop.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.listdrop.co
claude mcp add --transport http co-listdrop-listdrop 'https://www.listdrop.co/mcp'
{
"mcpServers": {
"co-listdrop-listdrop": {
"url": "https://www.listdrop.co/mcp"
}
}
} {
"servers": {
"co-listdrop-listdrop": {
"type": "http",
"url": "https://www.listdrop.co/mcp"
}
}
} [mcp_servers.co-listdrop-listdrop] url = "https://www.listdrop.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-listdrop-listdrop": {
"type": "remote",
"url": "https://www.listdrop.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-listdrop-listdrop --url 'https://www.listdrop.co/mcp' --transport streamable-http
mcp_servers:
co-listdrop-listdrop:
url: "https://www.listdrop.co/mcp" {
"McpServers": {
"co-listdrop-listdrop": {
"Transport": "http",
"Url": "https://www.listdrop.co/mcp"
}
}
} assistant mcp add co-listdrop-listdrop -t streamable-http -u 'https://www.listdrop.co/mcp'
{
"mcpServers": {
"co-listdrop-listdrop": {
"type": "http",
"url": "https://www.listdrop.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://www.listdrop.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.listdrop.co | CN=YR1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 55ea8f7a7c861e36052c4e458d25f25e4ca |
| SANs: www.listdrop.co | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.listdrop.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| listdrop.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self' |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.listdrop.co/mcp | Verified | 200 | |
| http (plaintext) | http://www.listdrop.co/mcp | HTTPS enforced | 301 | https://www.listdrop.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_list Save a list to ListDrop ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_emails | array | – | Email addresses allowed to VIEW this private list (view-only guest list). |
| description | string | – | – |
| emoji | string | – | – |
| expires_in_days | integer | – | Self-archive after this many days (list becomes owner-only). |
| items | array | yes | – |
| tags | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
get_list Read a public ListDrop list ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| list | string | yes | List URL or id |
No output schema declared.
No examples provided.
my_lists List the user's ListDrop lists ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_feedback Send feedback to the ListDrop team ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Only if your user wants a reply and gave you their address. | |
| kind | string | – | problem | idea | praise | other |
| message | string | yes | What happened, in plain words. Concrete beats polite: the call you tried, what you expected. |
No output schema declared.
No examples provided.
What is the ListDrop MCP server?
ListDrop is an MCP server listed in the public MCP registry as co.listdrop/listdrop. Save list-shaped answers as lists your user can keep, share, and check off. Keyless or OAuth. This page covers its hosted endpoint (https://www.listdrop.co/mcp).
Is the ListDrop MCP server safe to use?
ListDrop scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ListDrop MCP server expose?
ListDrop exposes 4 tools: create_list, get_list, my_lists, send_feedback. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.
Does the ListDrop MCP server require authentication?
No. We connected to ListDrop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ListDrop MCP server still maintained?
ListDrop is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.