_ registry / mcp http-sse · checked 2h ago

listdrop

https://www.listdrop.co

Registry code: 76ede247d753e603

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://www.listdrop.co/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is listdrop live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is listdrop free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does listdrop have?
4 tools: create_list, get_list, send_feedback, my_lists.
Is listdrop safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99%· all time 99%

latency
352ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 505 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • save a checklist
  • read a shared list
  • list my lists
takes → gives
text → web pages, text
tools
2 reads1 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 auth-required 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • my_lists reads auth-required 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • create_list changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "title",
        "items"
      ],
      "properties": {
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 8
        },
        "emoji": {
          "type": "string",
          "maxLength": 8
        },
        "items": {
          "type": "array",
          "items": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "object",
                "required": [
                  "text"
                ],
                "properties": {
                  "note": {
                    "type": "string",
                    "maxLength": 140
                  },
                  "text": {
                    "type": "string",
                    "maxLength": 200,
                    "minLength": 1
                  }
                }
              }
            ]
          },
          "maxItems": 50,
          "minItems": 1
        },
        "title": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1
        },
        "description": {
          "type": "string",
          "maxLength": 280
        },
        "allowed_emails": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "Email addresses allowed to VIEW this private list (view-only guest list)."
        },
        "expires_in_days": {
          "type": "integer",
          "maximum": 365,
          "minimum": 1,
          "description": "Self-archive after this many days (list becomes owner-only)."
        }
      }
    }
    arguments 73 lines
  • get_list reads unknown 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "list"
      ],
      "properties": {
        "list": {
          "type": "string",
          "maxLength": 300,
          "minLength": 6,
          "description": "List URL or id"
        }
      }
    }
    arguments 15 lines
  • send_feedback sends messages unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "message"
      ],
      "properties": {
        "kind": {
          "enum": [
            "problem",
            "idea",
            "praise",
            "other"
          ],
          "type": "string",
          "description": "problem | idea | praise | other"
        },
        "email": {
          "type": "string",
          "maxLength": 254,
          "description": "Only if your user wants a reply and gave you their address."
        },
        "message": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 4,
          "description": "What happened, in plain words. Concrete beats polite: the call you tried, what you expected."
        }
      }
    }
    arguments 30 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 76ede247d753e603.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/76ede247d753e603/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/76ede247d753e603/badge.svg)](https://brick.blue/agent/76ede247d753e603?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.