Servidor MCP de FnlOwl

• Nombre en el registrocom.fnlowl/fnlowlverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-24
• Herramientas40
• El servidor se llamafnlowl
• Versión del servidor0.1.0
• Versión del protocolo2025-06-18

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

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

• Parámetros sin descripción: en 27 de 40

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_projects

  Lists the projects this credential can act on. A project is one site or brand under the account, and every widget, lead, campaign and sequence belongs to one. Pass an id as the project argument on any tool to run that call in it, or as…

• create_project

  Creates a project — one more site or brand under the account — and returns its id. Pass that id as the project argument (or x-fnlowl-project / FNLOWL_PROJECT) to work inside it. Projects cannot be deleted from here.

• offer_choice

  Presents the user with a choice between 2 to 4 options, each with a label and a one-line description, one optionally marked recommended. It is for decisions where reasonable options would build different things — which widget kind, what…

• read_plan_usage

  Reads the account's plan and what it has used of each monthly quota: leads captured, emails sent, AI messages, plus how many websites and widgets exist against the plan's limits. Leads are counted over the billing period and everything…

• plan_site_strategy

  Gives an agent what it needs to advise on a website's lead capture: a snapshot of the website's widgets (kind, live or draft, views, completions, conversion), the six widget kinds with where each appears, and the steps to follow — read…

• list_widgets

  Every widget in the current project, newest last. Returns summaries only — id, name, kind, type, status, article, views, completions. Use read_widget for one widget's full content.

• read_widget

  One widget in full, plus `issues` — what is still missing before it could go live. Includes its questions, quiz questions and options, quiz tiers and calculator inputs. Which of those are meaningful depends on the kind: questions for…

• create_widget

  Create a widget in the current project. Six kinds: lead-magnet, popup, survey, announcement-bar, quiz, calculator. It is always created as a draft, and the result lists `issues` — what is still missing before it could go live (empty when…

• update_widget

  Change a widget. Only the fields sent are changed, with one exception: sending ANY of questions, quizQuestions, quizTiers or calcInputs replaces ALL FOUR with exactly what is sent, so send the complete set you want to end up with…

• request_widget_publish

  Ask for a draft widget to go live. This requests publication; it does not publish. Called over the API or MCP with a key it does NOT publish: it creates a pending approval carrying a before/after snapshot and returns it, and the widget…

• start_experiment

  Split traffic between a control widget and 1 to 3 variants. The variants must already exist as their own live widgets, of the same kind and project as the control (created with create_widget and made live with request_widget_publish). On…

• stop_experiment

  End a running experiment. Counts stop with it; starting a new one on the same widgets begins with fresh counts, not a resume.

• list_leads

  Captured leads for the current project, newest first. PAGED — at most 200 per call, and the limit is a hard cap, not a default you can raise; pass offset for the next page (limit 50 with offset 50 returns leads 51 onward). These rows are…

• read_lead

  One lead with the answers it gave, and its quiz score and tier if it came from a quiz. The score is frozen at the moment of submission — it is what that visitor actually saw, not a recomputation against the quiz as it stands today.

• read_analytics

  Totals for the current project: widget count, page views, completions, conversion percentage, lead count and how many have unsubscribed. Conversion is completions divided by views as a whole percentage; with no views yet it reads 0, which…

• list_widget_analytics

  The same numbers per widget, best-converting first. Use this to answer which magnet is working; use widget_results for where one widget's traffic came from.

• read_widget_results

  One widget's views, completions, conversion, and its leads grouped by referrer. The referrer is whatever the visitor's browser reported when they submitted, so it is a rough attribution, not a tracked source. Also returns the funnel…

• read_experiment_results

  The A/B experiment a widget is in (or last ran as control): per arm, assigned views, leads, conversion rate and 95% interval in basis points (1234 = 12.34%), and lift against the control arm. result "insufficient_data" means at least one…

• list_campaigns

  Campaigns in this project, newest first, with their status. Open and click numbers come from the sent-email ledger, not from a counter on the campaign.

• draft_campaign

  Create a campaign AS A DRAFT. There is no tool that sends one: sending puts mail in thousands of real inboxes, spends deliverability reputation that cannot be bought back, and cannot be undone. A person sends it from the dashboard…

• update_campaign

  Change a draft campaign. A campaign that has already been sent cannot be edited — the ledger describes what actually went out, and editing it afterwards would make that a lie.

• list_sequences

  Sequences in this project with their steps and branch. The shape is BOUNDED: a linear chain of steps, then at most one branch point, each path its own linear chain. No nesting, no rejoining, no parallel paths.

• list_sequence_enrollments

  Who is running through which sequence: for a lead (leadId) or for a sequence (sequenceId), each enrolment's status (active, finished or stopped), the step it is on and when it is next due. This is how to answer "why did this lead get, or…

• draft_sequence

  Create a sequence AS A DRAFT. Steps are either an email or a delay in days — a delay is its own step, so two emails can run back to back. A branch may be added at the end; its paths are evaluated first-match-wins, left to right, and a…

• update_sequence

  Change a DRAFT sequence. Only the fields sent are changed, except that sending steps or branch replaces the whole of that part, so send the complete chain you want. It cannot edit an active sequence and cannot activate one: an active…

• pause_sequence

  Move a sequence to draft, which stops new enrolments. Stopping mail is never the slower path, so this applies immediately. Starting one again is activate_sequence: an active sequence enrols every future lead and sends on a timer with…

• activate_sequence

  Activate a draft sequence so future matching leads are enrolled and may receive its emails. Activation starts timed sending with nobody watching, and the server does not itself verify human confirmation.

• list_templates

  Transactional templates in this account. Built-in starters are marked isCustom false and cannot be deleted.

• create_template

  Create a transactional template. category is one of authentication, account, orders, notifications. Use {{name}} placeholders in the subject and body for values supplied when it is sent; a placeholder nobody supplies is replaced with…

• update_template

  Change a template's name, category, subject or body — only the fields sent. Built-in starters can be rewritten too (they just cannot be deleted). It changes what later sends of this template say; it sends nothing.

• read_brand

  The brand: site name, accent colour, sender name, logo and the postal address that every commercial email needs in its footer. With a project in scope this is that website's brand — the account defaults with the website's own overrides…

• update_brand

  Change brand settings. Only the fields sent are changed. With a project in scope this sets that website's own override and leaves the account defaults — and every other website — alone; without one it changes the account defaults every…

• read_ai_context

  The account's AI context: what the blog is about, its pricing tiers, value props, testimonials, design direction and tone presets. Every AI-personalised lead magnet is generated from exactly this plus the visitor's own answers. It belongs…

• update_ai_context

  Change the AI context. This is the highest-leverage thing you can write here: it is tedious for a person to fill in and it improves every generation afterwards. Only the fields sent are changed. It holds what the site actually says, so…

• read_sending_status

  Read account sending readiness, domain verification, daily usage, and recent reputation state. While the sending domain is not yet verified it also returns `records`: the DNS records to publish. `sentToday` counts the last 24 hours on a…

• list_email_deliveries

  List recent email outcomes for this account. Recipients are masked; use this to diagnose queued, delivered, opened, clicked, bounced, complained, or failed mail. `sentToday` counts the last 24 hours on a rolling basis, while…

• list_integrations

  List native integration providers and connection health. Credentials are never returned.

• read_integration_delivery_status

  Read recent queued ESP/webhook handoff outcomes and retry state. Lead identifiers, payloads, and credentials are not returned.

• read_ai_generation_status

  Read recent AI lead-magnet generation outcomes by status and widget. Visitor answers, generated content, lead ids, and failure details are not returned.

• ask_question

  Ask the fnlowl Advisor a question in plain English. It knows how fnlowl works — widgets and where each kind appears, the embed, sequences, campaigns, sending, credits, plans, MCP — and can read the account's own widgets, leads, analytics…