Servidor MCP de Curated

• Nombre en el registronetwork.curated/curatedverificado en el registro MCP

El nombre en el registro está bajo curated.network. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-20
• Herramientas48
• El servidor se llamacurated
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-20 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 118 ms.

• Sus herramientas hacen todos los casos de uso comprobados: browse curators' lists to find books and films; build a private list of favourite tools.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta114 ms
• Espacio en el contexto del agente≈ 7527 tokenslas definiciones de todas sus herramientas (48), que el agente lleva en cada turno
• Definiciones de herramientasA · 96 de 100
• Resultados tipados0 de 48 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 11 de 48

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• account_context

  Verify 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_lists

  Return 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_list

  Create 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_list

  Edit 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_list

  Archive 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_list

  Bring an archived list back. It returns as a private list: going live again is a separate publish the person chooses.

• delete_list

  Delete 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_item

  Capture 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_items

  Add 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_url

  Import 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_import

  Bring 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_picks

  Add up to 1,000 more picks to an import started with start_import, for sources longer than one call.

• review_import

  Read an import's entries with their ids and states (kept, skipped, unsorted), to show the person or to sort.

• sort_import

  Keep 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_import

  Add 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_sources

  Show 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_source

  Read 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_items

  Read 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_items

  Search the curator's own picks by title or URL. Useful to check for a duplicate before add_item.

• update_item

  Edit 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_item

  Remove 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_items

  List 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_item

  Put 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_items

  Put 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_items

  Move 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_items

  After 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_status

  Read 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_items

  After 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_list

  Prepare 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_publication

  Publish 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_lists

  Search 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_lists

  Search live Curated lists by topic, title, or curator handle. Returns exact slugs; use get_list_items to read one.

• get_list

  Read 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_items

  Read 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_list

  Save 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_lists

  Read back Saved lists, matching the app. Each one brings its new picks.

• save_item

  Save 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_item

  Remove one pick from Saved picks. Idempotent. Never changes the list or the pick.

• saved_items

  Read 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_item

  Add 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_library

  The lists this person saved, each bringing its new picks. Their own lists are not included; use list_my_lists for those.

• search_library

  Search 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_updates

  What'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_updates

  Older 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_curator

  Explicitly follow or unfollow a curator by handle. Idempotent desired state, never a toggle. Does not save a list or enable email.

• curator_notifications

  Read 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_notifications

  Read 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_list

  Save a live free list with its new picks, only when the person asks. Same result as save_list. Idempotent; never charges anyone.