Servidor MCP de Sulvo

• Nombre en el registrocom.sulvo.publisher-revenue-audit/auditverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-20
• Herramientas41
• El servidor se llamapublisher-revenue-screen
• Versión del servidor0.3.4
• 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 100 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 MCP73 de 100responde 100 · definiciones 86 · contexto 71 · 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 respuesta90 ms
• Espacio en el contexto del agente≈ 8621 tokenslas definiciones de todas sus herramientas (41), que el agente lleva en cada turno
• Definiciones de herramientasB · 86 de 100
• Resultados tipados0 de 41 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 34 de 41

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 →

• check_https_certificate

  Check a publisher domain for HTTPS and certificate issues: expired/untrusted/hostname-mismatch certs, HTTPS down, HTTP that does not upgrade, and certs expiring within 14 days. Does not write a finding when both HTTP and HTTPS are…

• run_agentic_readiness_audit

  Free top-of-funnel scan: could a buyer agent find and buy this publisher? Checks adagents.json, standardized taxonomy tagging, audience segments in a readable schema, and a product/deals catalog. Returns what a buyer agent would see and…

• check_crawler_blocks

  Check whether robots.txt or a live probe blocks AmazonAdBot / Google ad crawlers. robots.txt Disallow and Amazon Crawl-delay are high-confidence fails. A WAF 403 against our scanner is a medium-confidence warn that needs verification.

• get_sulvo_boost_setup

  Instructions for setting up Sulvo Boost: first-party serving from the publisher's own CDN that recovers ad-blocked impressions. Covers Cloudflare, AWS and Fastly, plus the WordPress plugin for publishers who would rather not use a terminal.

• start_sulvo_revenue_onboarding

  Create or resume a verified-account activation workspace after the public audit and signup steps.

• get_sulvo_revenue_onboarding_status

  Return the backend-owned journey stage, readiness dimensions, and one next best action.

• attach_sulvo_revenue_audit

  Attach a current public revenue audit artifact. Input requires expectedVersion and auditArtifactId.

• connect_sulvo_backup_provider

  Return the GAM or AdSense authorization URL. Input requires provider set to gam or adsense.

• import_sulvo_backup_units

  Import connected provider units. Input requires provider and expectedVersion.

• review_sulvo_placement_recommendations

  Save accept, edit, or reject decisions. Input requires expectedVersion and decisions.

• save_sulvo_placement_plan

  Save a placement revision. Input requires expectedVersion and payload.

• map_sulvo_placement_backup

  Map a display placement backup. Input requires expectedVersion, stablePlacementId, provider, and providerId.

• get_sulvo_installation_instructions

  Return installation values for the locked revision. Input is empty.

• verify_sulvo_placement_installation

  Verify every stable placement container and the inert loader for the locked revision.

• lock_sulvo_placement_revision

  Lock the exact mapped revision. Input requires expectedVersion and revisionId.

• run_sulvo_activation_preflight

  Run the complete bounded activation preflight for the locked workspace revision.

• verify_sulvo_site_ownership

  Verify the required ads.txt and inert Sulvo head-tag ownership evidence.

• submit_sulvo_activation_workspace

  Submit the proven revision. Input requires expectedVersion and revisionId.

• submit_sulvo_site_for_approval

  Retag-after-approval journeys: submit the bare site for Google approval (ads.txt ownership only, no tags). Input requires expectedVersion.

• set_sulvo_onboarding_journey

  Set or change the journey intake answers on the workspace. Input requires expectedVersion plus at least one of mode, goal, retagTiming.

• rollback_sulvo_activation

  Return the workspace domain to publisher-owned backup-only serving.

• get_sulvo_activation_smoke_status

  Return active-probe, real-page, and remediation status for the latest activation attempt.

• run_publisher_revenue_audit

  Run a public publisher revenue-readiness screen using directional public evidence. Audits ad stacks, ads.txt hygiene, consent readiness, PageSpeed metrics, and unblocked premium ad unit opportunities (such as Sulvo) to recover lost yield.

• apply_for_sulvo_account

  Submit an unauthenticated Sulvo account application lead through the current signup API. Audit tools remain available without login, API key, or OAuth; ad-unit generation should wait for Sulvo account approval.

• start_sulvo_signup

  Run normal Sulvo signup step 1: verify the publisher domain and create the unauthenticated signup lead.

• create_sulvo_signup_account

  Run normal Sulvo signup step 2: create the pending Sulvo user/account. The current signup backend requires a password before the account can continue to ads.txt and review.

• update_sulvo_signup_company

  Run normal Sulvo signup step 3: save optional company information for a pending Sulvo signup.

• get_sulvo_signup_ads_txt

  Run normal Sulvo signup step 4a: fetch the ads.txt lines the publisher must add for site ownership verification.

• verify_sulvo_signup_ads_txt

  Run normal Sulvo signup step 4b: verify whether the submitted publisher domain has the required Sulvo ads.txt lines.

• get_sulvo_signup_status

  Return the current signup status capability. The current signup API has no public approval-status endpoint, so this tool reports that limitation instead of guessing approval state.

• submit_sulvo_signup_documents

  Explains how to complete Sulvo signup document review. Document submission is done in Sulvo onboarding - upload monthly earnings proof or connect an AdSense account - not through this connector, which has no access to the user's local…

• get_publisher_revenue_audit_checklist

  Return the public checklist and interpretation notes used by the publisher revenue-readiness screen.

• get_publisher_monetization_benchmarks

  Get comparative yield and CPM industry benchmarks by publisher vertical to compare standard stacks (AdSense and managed wrappers) against Sulvo Premium Ad Units.

• create_sulvo_ad_unit

  Create a Sulvo ad unit for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment, never passed as an argument — an account owner mints a write-scoped key in the Sulvo dashboard (Account…

• create_sulvo_interstitial_units

  Create Sulvo interstitial ad units (tagless) for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.

• create_sulvo_auto_sticky_units

  Create Sulvo auto-sticky ad units for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.

• delete_sulvo_ad_unit

  Delete a Sulvo ad unit by id for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment. The key's account must own the unit; the backend enforces ownership.

• get_sulvo_report

  Fetch a Sulvo report (read-only). Requires SULVO_API_KEY in the server environment (a publisher generates it in the dashboard: Account Settings -> API key). Covers by-date, by-date-and-ad-unit, by-domain-and-ad-unit, bot-filtering…

• list_sulvo_advanced_reports

  List the saved Sulvo advanced reports for the account. Requires SULVO_API_KEY (with the reports:read scope) in the server environment.

• save_sulvo_advanced_report

  Create/update a Sulvo advanced report (adUnit, dimensions, or customData), run immediately (emailed) or on a recurring schedule. Requires SULVO_API_KEY (with the reports:write scope) in the server environment. Note: advanced reports are…

• delete_sulvo_advanced_report

  Delete a saved Sulvo advanced report by id. Requires SULVO_API_KEY (with the reports:write scope) in the server environment.