Servidor MCP de Howseen AI

• Nombre en el registroai.howseen/howseen-mcpverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-27
• Herramientas29
• El servidor se llamahowseen
• Versión del servidor1.2.0
• Versión del protocolo2025-06-18

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

• Sus herramientas hacen todos los casos de uso comprobados: track which brands AI assistants recommend for buyer questions; see which sources and pages AI engines cite; draft and publish articles so AI engines cite your site.
• 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
• Qué puede hacer un agente con él3 de 3 casos de uso
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta290 ms
• Espacio en el contexto del agente≈ 6366 tokenslas definiciones de todas sus herramientas (29), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados0 de 29 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

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 →

• list_brands

  List the brands (websites) tracked in this Howseen account, with their id, name and domain. Call this first when the account may have several brands.

• get_visibility

  Headline AI visibility of a brand: % of AI answers that name it, share of voice vs competitors, average position, sentiment, per engine, plus the trend over the period (one point per scan).

• list_prompts

  The buyer questions (prompts) tracked for a brand, with per-prompt visibility, share of voice, position, which engines name the brand, and which brands and domains are cited.

• get_competitors

  Compare the brand with its competitors in AI answers: visibility %, share of voice, average position and sentiment, overall and per engine.

• get_top_sources

  The domains and URLs AI engines cite most when answering the brand's buyer questions, overall and per engine. Use it to find where the brand should get listed or mentioned.

• search_responses

  Read real AI answers collected for the brand: excerpts around the brand mention, whether the brand and which competitors were named, and the cited URLs. Filter by a word in the question or answer (query), by prompt text, and by engine.

• get_action_plan

  Prioritized actions to raise the brand's AI visibility (off-page: get listed on the pages AI cites; content: answer uncovered buyer questions), ranked 20/80 like the dashboard Action plan, with steps.

• list_articles

  Articles Howseen wrote for the brand (drafts, scheduled and published), with status, target question, GEO score and published URL.

• get_prompt_gaps

  Tracked prompts where AI names at least one competitor but not the brand, per engine, with the competitors named and the domains cited. Sorted by search volume (when a cached figure exists) then by number of competitors named. Start here…

• get_easiest_wins

  Third-party sites and pages cited in the answers the brand loses (competitor named, brand not), ranked by how many lost answers cite them, with the matching action-plan item. Getting listed there is the shortest path back into those…

• get_changes

  What changed between the last two completed scans (or since a date): prompts gained and lost, visibility delta per engine, tracked competitors newly named, and the likely causes (sources that started or stopped citing the brand).

• suggest_prompts

  Buyer questions worth tracking that the brand does not track yet: real questions from Hacker News discussions (ranked by engagement) plus AI suggestions for the category. Returns suggestions only; use add_prompts to track some. Limited to…

• get_article_performance

  Articles written for the brand with status, GEO score, published URL and search-engine indexing status (Google URL Inspection, Bing), plus impressions and clicks when Search Console or Bing is connected.

• get_usage

  Plan, quotas used and left (prompts, competitors, articles, manual scans), next automatic scan estimate, what this API key may do, and the API rate limits. Call it before planning changes.

• mark_action_done

  Mark an action-plan item as done (same state as the dashboard Action plan). Use the action id from get_action_plan or get_easiest_wins. Preview first; confirm: true applies.

• dismiss_action

  Dismiss an action-plan item the user does not want to do (moves it to Archived in the dashboard, out of the next best actions). Reversible in the dashboard. Preview first; confirm: true applies.

• add_prompts

  Track new buyer questions (prompts) for the brand, checked against the plan's prompt quota (the whole list is refused if it would exceed it). An archived prompt added again is restored. Preview first; confirm: true applies.

• remove_prompts

  Stop tracking prompts and remove them from the prompt list (past scan results stay in history). Prefer archive_prompts to keep them listed. Preview first; confirm: true applies.

• archive_prompts

  Archive prompts: they stop being scanned (frees prompt quota) but keep their history and stay listed as archived in the dashboard, restorable. Preview first; confirm: true applies.

• add_competitor

  Track a competitor from a name or a website URL (resolved to name + domain like in Settings), within the competitor quota. Preview first; confirm: true applies.

• remove_competitor

  Stop tracking a competitor (by name or domain). Past results keep it. Preview first; confirm: true applies.

• draft_article

  Write a DRAFT article answering one buyer question, with the same quality pipeline as the app (brand context, sources AI cites, GEO checks). Never publishes. Uses the plan's article allowance. Preview first; confirm: true writes it (up to…

• refresh_article

  Rewrite a WRITTEN article with the brand's current profile (offer, category, offerings, competitors) after it changed: same article id, slug, question and date, previous version kept (restorable in the app). A published article is never…

• create_share_report

  Create a public, frozen report link (visibility, competitors, top prompts, recommendations) with the account's agency branding, like the dashboard Share button. Preview first; confirm: true creates the link.

• run_scan

  Scan the brand's prompts on the AI engines now, with the same limit as the dashboard Run now button (a fresh scan at most once per brand per plan cadence: every 72h, every 24h on Business; prompts added since the last scan can be scanned…

• publish_article

  Publish a written article (e.g. a draft from draft_article) to the brand's connected CMS (WordPress, Shopify, Ghost, BigCommerce, GoHighLevel, Webflow, webhook) or hosted blog, now, or schedule it for a later date (needs Autopilot ON)…

• request_indexing

  Submit a published article to the search engines connected for the brand: Google (sitemap re-submit through Search Console when connected with indexing), Bing (Webmaster key) or IndexNow for pages hosted by Howseen. If you publish on your…

• delete_article

  Move an article (planned, draft or published) to the Trash, like the dashboard delete button: restorable with restore_article or in Howseen > Content > Trash, and its topic is not planned again. A post already live on the client's own CMS…

• restore_article

  Bring back an article from the Trash (e.g. one deleted with delete_article). Preview first; confirm: true restores.