Servidor MCP de DigitalPublic

• Nome no registrocom.digitalpublic/commercialverificado no registro MCP

O nome no registro fica sob digitalpublic.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-24
• Ferramentas27
• O servidor se chamadigitalpublic-commercial
• Versão do servidor2026-09-10-trial-active-projects-v1
• Versão do protocolo2025-06-18

Em 2026-10-24 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 545 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta620 ms
• Espaço no contexto do agente≈ 3.040 tokensas definições de todas as ferramentas (27), que o agente carrega a cada turno
• Definições das ferramentasB · 86 de 100
• Resultados tipados27 de 27 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 22 de 27

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e 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, exige loginverificado no registro MCP