Servidor MCP de Bot Appétit

• Nombre en el registroai.botappetit/bot-appetitverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-11-02
• Herramientas14
• El servidor se llamabot-appetit
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-11-02 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 425 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 1 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: 1 hasta ahora
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta663 ms
• Espacio en el contexto del agente≈ 2391 tokenslas definiciones de todas sus herramientas (14), que el agente lleva en cada turno
• Definiciones de herramientasB · 83 de 100
• Resultados tipados0 de 14 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Sin indicar si solo lee o puede destruir: 14 de 14

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 →

• scan_page

  Check one web page for AEO, SEO and performance: can a machine consume it? Returns the findings by check and the report link. If the exact page was scanned in the last 24 hours the stored result is returned at no cost; set fresh to scan…

• get_report

  Get a stored Bot Appétit report by scan id, the same report a person sees at botappetit.ai/r/<id>. Costs nothing and does not scan. Use it to re-read a report you were given a link to. A page that blocked our scanner is returned as…

• page_history

  List every stored Bot Appétit scan of one exact page, newest first, with the score at the time and how it moved since the scan before. Costs nothing and does not scan. Use it to show whether a page has improved. Blocked and failed scans…

• list_checks

  List every check Bot Appétit runs on a page, grouped by category, with the id of each. Use the id with explain_check for what a check means and what good looks like. Every check asks one question: can a machine consume this page?

• explain_check

  Explain one Bot Appétit check: what it looks at, why it matters for machines reading a page, and what good looks like. Use the id from list_checks or a report. Costs nothing and does not scan.

• request_site_scan

  A whole-site scan reads a representative sample of a site and needs a person with a Bot Appétit account, and an agent never creates one. This returns exactly what the person must do, in order: connect this agent to their account (a…

• leaderboard

  The highest-scoring sites by category, from the latest Bot Appétit scan of each site's homepage: rank, host, score out of 100, grade and a link to the full report. Call it with no category to see the top of every category, or with a…

• start_site_scan

  Start a whole-site scan for the signed-in person's account: Bot Appétit reads a representative sample of the site (not every page) and scores it. Needs the person to have authorised this connection. It returns a job_id straight away; the…

• site_scan_status

  Read one of the signed-in person's site scans: whether it is still running, and once it has finished the score, the checks that failed, the category scores and the pages it covered, each page with a link to its own full report. Only the…

• list_sites

  List the sites the signed-in person follows in Bot Appétit, newest activity first, each with its latest site-scan score, the change since the scan before, and the trend. Use a host from here with site_history, set_pins and the other site…

• site_history

  Read one of the signed-in person's sites over time: every site scan of it newest first with the score and the change since the previous scored scan (a change across a scoring update or different pinned pages is marked, not passed off as…

• set_pins

  Pin or unpin pages on one of the signed-in person's sites. Pinned pages are scanned in every site scan of that site and count toward its score; up to 25, on the site itself. Give pin and/or unpin lists. Returns each address's outcome and…

• set_rescan_settings

  Turn the signed-in person's monthly re-scans of their sites on or off, and the email of each result on or off. Leave a field out to keep it as it is; call with no fields to read the current settings. The settings belong to the account…

• share_site_scan

  Create or stop the unlisted share link for one of the signed-in person's site scans. Site scans are private by default; a link lets anyone who holds it read that one scan (not the person's other scans) and stays valid until stopped. Only…