Servidor MCP de DigitalPublic

• Nombre en el registrocom.digitalpublic/commercialverificado en el registro MCP

El nombre en el registro está bajo digitalpublic.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
• Herramientas27
• El servidor se llamadigitalpublic-commercial
• Versión del servidor2026-09-10-trial-active-projects-v1
• 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 545 ms.

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

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

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 (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). 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 →

• dp_commercial_get_company_profile

  Return the verified legal identity, corporate contacts, and evidence URLs for DigitalPublic.

• dp_commercial_ask_navigator

  Match a prospective need with public DigitalPublic capabilities, illustrative use cases and plans. It has no access to customer projects or private data.

• dp_commercial_get_capability_matrix

  List read, preparation, supervised-write, approval, plan, and module capabilities with explicit qualifications.

• dp_commercial_get_data_processing_profile

  Explain controller and processor roles, public AI training policy, private customer data exclusions, controls, DPA, privacy, and subprocessor evidence URLs.

• dp_commercial_compare_integration_options

  Provide an objective comparison of direct provider MCP servers and DigitalPublic across setup, governance, cross-channel work, and tradeoffs.

• dp_commercial_estimate_roi

  Calculate only the value of entered time savings, plan cost, net value, and break-even hours. It never forecasts sales or advertising performance.

• dp_commercial_list_use_cases

  List clearly labeled illustrative use cases without presenting them as customer results or performance claims.

• dp_commercial_get_service_status

  Return the current component health and timestamp. Status is measured by an independent monitor hosted outside the platform. Components with no recent evidence are reported as 'unknown' — never assume 'unknown' means healthy. Does not…

• dp_commercial_get_uptime_history

  Return historical uptime for a component, always alongside its data coverage. A high uptime with low coverage is not meaningful, so both values must be reported together. Returns 'insufficient_data' when coverage is too low to publish a…

• dp_commercial_start_live_trial

  Start an idempotent 14-day trial with up to three active real projects, 2,000 total units, up to five connected tools and supervised write access. Sensitive actions still require human approval. A single passwordless email verifies…

• dp_commercial_get_live_trial_status

  Resume a trial using its limited status token. Returns stable state and nextAction, remaining days, units and connection capacity, plus only safe human links. It never returns email, provider tokens, OAuth URLs, or provider payloads.

• dp_commercial_get_install_options

  Return publication-aware installation options for the authenticated DigitalPublic operational product in OpenAI, Claude Code, and generic MCP clients. Directory URLs remain null until publication is explicitly enabled.

• dp_commercial_get_onboarding_guide

  Return the goal-oriented sequence an agent should follow, including every mandatory human checkpoint and the handoff from DigitalPublic Commercial to DigitalPublic.

• dp_commercial_describe_platform

  Explain what DigitalPublic does for humans and AI agents.

• dp_commercial_list_offers

  List current plans, EUR and USD prices, limits, seats, modules, and checkout mode.

• dp_commercial_get_offer

  Return one current plan by id.

• dp_commercial_compare_offers

  Compare two or more plans using the canonical catalog.

• dp_commercial_assess_fit

  Recommend a plan from project count, team size, live-data need, distributor status, and write requirement.

• dp_commercial_list_integrations

  List integrations included in commercial V1. Use trialChannels, not the connector id, as channels for dp_commercial_start_live_trial.

• dp_commercial_get_connection_requirements

  Explain authentication modes, scopes, human prerequisites, review state and known limitations for one DigitalPublic connector.

• dp_commercial_get_security_profile

  Explain project isolation, scopes, approvals, token revocation, and audit controls.

• dp_commercial_get_checkout_readiness

  Report whether the real trial, self-service checkout, and Enterprise proposal onboarding are currently available.

• dp_commercial_get_sample_report

  Return an illustrative synthetic report sample without customer data. This is not a service trial and must never be represented as measured customer performance.

• dp_commercial_start_checkout

  Compatibility checkout for paid plans and Enterprise proposals. Use dp_commercial_start_live_trial for evaluation. A human must verify email and complete any payment.

• dp_commercial_get_checkout_status

  Return the non-sensitive status of a historical checkout or proposal request. For the real trial use dp_commercial_get_live_trial_status.

• dp_commercial_claim_credentials

  Legacy credential claim for still-valid historical paid checkout intents. Live trials never deliver an operational credential in chat; install DigitalPublic and use project OAuth instead.

• dp_commercial_request_proposal

  Request an email-verified Enterprise proposal. This does not create a contract or charge.

• com.digitalpublic/marketing-operationsresponde, pide iniciar sesiónverificado en el registro MCP