Servidor MCP de ViewPrinter

• Nombre en el registrotech.viewprinter/viewprinterverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-18
• Herramientas16
• El servidor se llamaviewprinter
• Versión del servidor1.1.0
• Versión del protocolo2025-06-18

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

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.

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 MCP75 de 100responde 100 · definiciones 96 · contexto 65 · conexión 100 · rebajada por las señales de aviso de abajo
• Respondióel 100% de los días9 de 9 comprobaciones diarias
• Mediana de la primera respuesta271 ms
• Espacio en el contexto del agente≈ 11.110 tokenslas definiciones de todas sus herramientas (23), que el agente lleva en cada turno
• Definiciones de herramientasA · 96 de 100
• Resultados tipados23 de 23 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 5 de 23

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 (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). 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 →

• platforms_list

  What each platform accepts. Called with nothing, it lists every platform with the media kinds and counts it takes and its caption limit — enough to decide where a post can go. Name platforms to add their recommended sizes and durations…

• accounts_list

  List every social account you can post to, across all your workspaces. Each account includes the workspace it belongs to and any groups it is in. Use the returned ids to name post destinations explicitly, or a group name to name several…

• accounts_connect

  Connect a social account. Opens the platform in the person's browser so they can sign in and approve access — that part cannot happen here, because it needs their session and their consent. Call it again after they finish and it reports…

• products_list

  The products your accounts post for — an app, a book, a shop — each with the accounts linked to it and the workspace it is in. An account belongs to at most one product. Use products_save to create one or change which accounts belong to it.

• products_save

  Create a product, or change one. Found by id when given, otherwise by name (ignoring case) and created when there is none, so saving the same product twice changes nothing the second time. account_ids is the complete list of accounts that…

• products_delete

  Delete a product. Its accounts stay connected and belong to no product afterwards. Refused while it has campaigns. Its knowledge documents and gathered research are deleted with it, so this is refused while it has any unless…

• groups_list

  Your named sets of accounts. Each group lists its members with the state of each, and how many of them need reconnecting — a post naming a group is refused outright if any member cannot publish, so check here before composing one. Use a…

• groups_save

  Create a group or change one. A group is a name for a set of accounts, so posts_save can take the name instead of every id. Found by name without regard to case: an existing group is updated (new_name renames it), and a new name creates…

• groups_delete

  Remove a group. The accounts in it are not touched and stay connected — only the name and its membership go. Posts already scheduled through it are unaffected, because a post records the accounts rather than the group.

• media_upload

  Get a file into ViewPrinter, under an id you can pass to posts_save, media_save or anything else that takes a media id. If the person attached the file in this chat, or has it on their phone or computer, call this with no arguments, as an…

• media_list

  Files in your workspaces, newest first, 50 at a time. Use these ids when attaching media to a post. By default these are the files to post; purpose: source lists the raw material kept to reuse instead. Narrow with kind, tags (files…

• media_save

  Say what a file is, in your own words. description is what it shows: on a base image, who is on camera — "a woman in her early twenties, blonde hair in a loose bun" — and a campaign reads it so the same person appears in every render…

• media_delete

  Remove a file and its stored bytes. This cannot be undone. A file a post still uses cannot be removed, and neither can raw material kept with purpose source: switch it to library with media_save first.

• research_ask

  Ask a question about your niche and get back the posts that answer it. Give question and product_id and it starts searching for that question, which takes a few minutes, and returns at once with a thread_id and status working. Call it…

• posts_save

  Create, change or cancel a post. This publishes: a new post is queued for every account named and goes out at scheduled_at, or as soon as possible without one. Do not tell anyone their post is saved or scheduled until this has returned…

• posts_list

  Posts in your workspaces, newest first, one page at a time, each with the state of every destination it was sent to and the numbers it has earned so far. Call it to find one post (post_id), to check whether something published, and before…