
Curated MCP server
Which servers in the official MCP registry are Curated's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry namenetwork.curated/curatedverified in the MCP registry
The registry name sits under curated.network. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-20
- Tools48
- Server calls itselfcurated
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 118 ms.
- Its tools do every use case we checked: browse curators' lists to find books and films; build a private list of favourite tools.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- For "build a private list of favourite tools", the likely first call is create_list.
- add_item, add_items, update_item, remove_item, add_saved_item change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer114 ms
- Space in an agent's context≈ 7,527 tokensthe definitions of all its tools (48), which an agent carries on every turn
- Tool definitionsA · 96 of 100
- Typed results0 of 48 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 11 of 48
What an agent can do with it
- can do · browse curators' lists to find books and films
- can do · build a private list of favourite tools
- not sure · follow designers and critics for a steady stream of picks
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: add_item, add_items, update_item, remove_item, add_saved_item
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
account_contextVerify the connected account and its readiness before creating or changing lists. Returns account requirements, recovery URLs and what this connection may do. Never ask for a token in chat.
list_my_listsReturn the person's own lists (slug, title, status, Inbox flag) and the lists they have access to. Call before add_item when unsure which list to target.
create_listCreate a new private list and return the exact slug to reuse in add_item. Repeating the same request dedupes instead of creating another recent list.
update_listEdit a list's title, subtitle, or category. Saves the working version without publishing. Readers keep seeing the last approved version until the owner approves a list update.
archive_listArchive one of the person's lists: it leaves their profile, search and readers' view, and its page stops working. Nothing is lost; unarchive_list brings it back. Confirm with the person first.
unarchive_listBring an archived list back. It returns as a private list: going live again is a separate publish the person chooses.
delete_listDelete one of the person's lists for good. It disappears for them and for readers and cannot be brought back. Refused for Inbox. Only after the person asks to delete that exact list by name; offer archive_list when they may want it back.
add_itemCapture one pick with the person's own note. Omit `list` only to deliberately use Inbox. An ambiguous or missing list writes nothing and returns candidates; ask the person, or set `create_if_missing` when they explicitly want a new list…
add_itemsAdd up to 50 picks to one list in a single call, in order. Unlike add_item this never falls back to the Inbox: `list` must resolve to exactly one of the curator's lists or nothing is written.
import_from_urlImport picks into a list from one link: a Google Maps list shared with "Anyone with the link" (every place, in order, with the owner's notes; pasting it again adds only new places), a Google Maps place (one pick) or a public YouTube…
start_importBring a whole list in to sort, privately. Pass `url` for a Google Maps list shared with "Anyone with the link" (Curated reads every place), or `picks` you read yourself from anywhere else: a page, an account, a document or an export (up…
stage_picksAdd up to 1,000 more picks to an import started with start_import, for sources longer than one call.
review_importRead an import's entries with their ids and states (kept, skipped, unsorted), to show the person or to sort.
sort_importKeep or skip entries in an import, by id or all unsorted at once, as the person decides. Never decide for them which posts are recommendations; suggest, then ask.
commit_importAdd the kept entries of an import to a list, privately: the list given at start_import, another list of theirs, or a new private list. Safe to retry; nothing is added twice. A Google Maps list can stay connected so new saves there show up…
list_sourcesShow what one of the person's lists is connected to: when it was last checked, what is new and waiting, and what is gone at the source.
check_sourceRead a connected list's source again now (up to 10 times a day per list). New entries arrive by the list's policy; nothing is removed.
list_itemsRead every pick in one of your lists, in reader order, with item ids. Call this before update_item or remove_item to get the id you need.
search_itemsSearch the curator's own picks by title or URL. Useful to check for a duplicate before add_item.
update_itemEdit one pick's title, curator note, URL or author. The note is the curator's own words and is never rewritten by AI, so preserve their voice.
remove_itemRemove one pick from a list. Curated keeps it with its note, links and saves, and restore_item puts it back. Confirm with the curator first. Changes the working version only; readers keep seeing the last approved version until the owner…
removed_itemsList picks removed from one of the person's lists that have not been put back, newest first, with their notes and ids for restore_item. Follow nextCursor as cursor to reach older picks.
restore_itemPut a removed pick back on its list where it was, with the same id, note, details, links and saves. Changes the working version only; readers keep seeing the last approved version until the owner approves a list update.
reorder_itemsPut a list's picks in a new order. Pass every item id exactly once, first to last, and the `revision` from list_items; if the list changed since, nothing is written and the current revision comes back. Changes the working order only…
move_itemsMove picks from one of the person's lists to another, keeping each pick's note, details and history. They go to the end of the destination in the order given. Pass the source list's `revision` from list_items; if it changed since, nothing…
review_itemsAfter adding or importing picks, fetch their enriched preview here. If preparing, wait briefly and call again. Render previewMarkdown: supplied artwork, title/byline, original note, short description and labeled links for every pick. Keep…
pick_review_statusRead whether an exact pick preview was already confirmed, is pending, or expired. Use when reopening a previous preview or checking a lost confirmation response. Never adds picks, starts enrichment, or changes the review. Keep reviewId…
confirm_itemsAfter the person approves the enriched preview from review_items, finish adding those exact picks. Published lists show them immediately; private lists stay private. Never approves unrelated edits. Requires lists.publish only for a…
publish_listPrepare first publication or a list-wide update. For new picks use review_items and confirm_items during addition. Publishes nothing. Returns exactly what would become public and, when this connection may publish from chat, a review to…
confirm_publicationPublish the exact list the owner reviewed, after they explicitly agree to that summary in this conversation. Never on an earlier general instruction like 'publish when done'. If anything changed since the review, nothing is published and…
search_listsSearch every live list on Curated, not just the person's own. Each result carries `access` (yours, unlocked or locked) and a `ref` of the form handle/slug, the unambiguous way to name a list in get_list.
find_listsSearch live Curated lists by topic, title, or curator handle. Returns exact slugs; use get_list_items to read one.
get_listRead one list: every pick of a live list, or of one of the person's own. Accepts handle/slug, a bare slug, a title, or an id.
get_list_itemsRead one list and report each pick's details status. The capture read-back check; use the exact slug returned by create_list or list_my_lists.
save_listSave a live list to Library under Saved lists, with its new picks. Never follows the curator, turns on email or publishes. Idempotent across retries.
saved_listsRead back Saved lists, matching the app. Each one brings its new picks.
save_itemSave one pick from a list you can read, yours or anyone's, to Library under Saved picks. Use the item id from get_list_items or list_items. Does not copy the pick, follow or publish. Idempotent across retries.
unsave_itemRemove one pick from Saved picks. Idempotent. Never changes the list or the pick.
saved_itemsRead back your saved picks across every list, newest first, matching Saved picks in the app. Separate from saved_lists and from my_library access.
add_saved_itemAdd a pick you can read, usually one from saved_items, to one of your own lists as a new pick. Carries the facts (title, link, place, type) and records where it was found; the note starts empty because the source curator's words are…
my_libraryThe lists this person saved, each bringing its new picks. Their own lists are not included; use list_my_lists for those.
search_librarySearch inside the lists this person has access to: "what was that ramen place from the Tokyo list?". Only searches lists they can read in full.
library_updatesWhat's new in the lists this person has access to since a point in time. Defaults to the last 7 days. Pass the returned `checkedAt` back as `since` next time for a gap-free diff.
get_list_updatesOlder name for save_list on a live free list: saves it to Library with its new picks. Only when asked. Idempotent; no curator follow, email or payment. Read back with saved_lists.
follow_curatorExplicitly follow or unfollow a curator by handle. Idempotent desired state, never a toggle. Does not save a list or enable email.
curator_notificationsRead a followed curator's email preference, or set `enabled` only on an explicit email request. Follow is separate consent; list access and bookmarks are unchanged.
list_notificationsRead every notification setting when `push` and `email` are omitted. Only on an explicit request, set push and/or email about new picks on one list the person gets updates for. Never changes access, saves or follows.
unlock_listSave a live free list with its new picks, only when the person asks. Same result as save_list. Idempotent; never charges anyone.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"curated": {
"type": "http",
"url": "https://mcp.curated.network"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http curated https://mcp.curated.networkclaude.ai, ChatGPT and other clients: add https://mcp.curated.network as a custom connector in the settings.
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.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.