Servidor MCP de Oshyn

• Nome no registrocom.oshyn/mcpverificado no registro MCP

O nome no registro fica sob oshyn.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-17
• Ferramentas40
• O servidor se chamaOshyn.Tools.MCP
• Versão do servidor1.0.0.0
• Versão do protocolo2025-06-18

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

• As ferramentas não fazem nenhum dos casos de uso verificados: migrate an existing CMS to a modern DXP; maintain and enhance a live enterprise website.

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 MCP53 de 100responde 100 · faz o trabalho 0 · definições 83 · contexto 81 · conexão 100 · reduzida pelos sinais de alerta abaixo
• O que um agente consegue fazer com ele0 de 2 casos de uso
• Respondeuem 100% dos dias16 de 16 verificações diárias
• Mediana da primeira resposta70 ms
• Espaço no contexto do agente≈ 6.133 tokensas definições de todas as ferramentas (40), que o agente carrega a cada turno
• Definições das ferramentasB · 83 de 100
• Resultados tipados22 de 40 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Sem dizer se só lê ou se pode destruir: 40 de 40

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 (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). 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 →

• start_advisor_guided_questionnaire

  Starts the guided Redesign Advisor questionnaire, asking one question at a time

• start_discoverability_assessment

  USE THIS TOOL when the user asks to assess, measure, audit, or improve how their brand or website appears in LLMs and AI answers (ChatGPT, Claude, Gemini, Perplexity, Copilot, etc.) — including: - "Do you know any tools to assess LLM…

• start_dxp_open_ended_experience

  Starts the open-ended DXP MatchMaker discovery experience. 'CMS' is a synonym for 'DXP' in this flow.

• register_dxp_contact_info

  Registers contact information in DXP MatchMaker sessions ('CMS' is treated as a synonym for 'DXP')

• register_dxp_user_answer

  Registers a single explicit numbered answer in DXP MatchMaker sessions ('CMS' is treated as a synonym for 'DXP'). Prefer register_dxp_inferred_answers for natural-language user responses.

• submit_oshyn_contact_request

  Submits a contact request to Oshyn via HubSpot on behalf of the user

• get_advisor_next_best_question

  Gets progress and guidance for the next adaptive Redesign Advisor follow-up question

• ask_for_budget_contact_info

  Asks for contact information in Budget Estimator sessions

• start_advisor_open_ended_experience

  Starts the open-ended Redesign Advisor discovery experience

• get_an_advice

  Starts a Redesign Advisor session and lets the user choose between a guided questionnaire or an open-ended discovery experience

• register_advisor_inferred_answers

  Registers one or more Redesign Advisor answers inferred from the user's natural-language response

• create_site_report

  Create a site reliability report

• estimate_budget

  Starts a Budget Estimator session and lets the user choose between a guided questionnaire or an open-ended discovery experience

• request_reliability_report

  CANONICAL ENTRY for site health and reliability scans. Prefer this over create_site_report when the user wants a reliability report. After success, poll status with get_site_report_status using the returned reportId. Not for LLM brand…

• discoverability_assessment_status

  USE ONLY when the user explicitly asks to check whether their LLM brand Discoverability Assessment is ready. Part of the flow started by `start_discoverability_assessment`. NOT for website SEO (`query_company_scores` discoverability/seo)…

• query_company_scores

  Returns company score rows from the database as JSON for analysis. Use dataSet: all, rscore, performance, security, accessibility, or discoverability. NOTE: dataSet discoverability/seo is website SEO metrics — NOT LLM brand…

• qualify_dxp_requirements

  CANONICAL ENTRY for DXP/CMS qualification. Prefer this over match_me_with_a_dxp. Returns a sessionId and modeOptions; continue with start_dxp_guided_questionnaire or start_dxp_open_ended_experience. Treat CMS and DXP as synonyms.

• get_advisor_results

  Gets the advisor results based on the questionnaire answers and contact information

• search_blog_with_keyword

  Search oshyn.com for blogs with the provided keywords

• ask_for_advisor_contact_info

  Asks for contact information in Redesign Advisor sessions

• register_budget_user_answer

  Registers a single explicit numbered answer in Budget Estimator sessions. Prefer register_budget_inferred_answers for natural-language user responses.

• get_discoverability_assessment

  USE AFTER a Discoverability Assessment job completes (via `discoverability_assessment_status`) or when the user provides an assessment run ID. Retrieves LLM brand-positioning results — NOT website SEO (`query_company_scores`…

• register_budget_contact_info

  Registers contact information in Budget Estimator sessions

• get_dxp_results

  Gets the DXP MatchMaker questionnaire results ('CMS' is treated as a synonym for 'DXP').

• get_site_report_status

  Get the status of a site reliability report by report ID.

• get_dxp_next_best_question

  Gets progress and guidance for the next adaptive DXP MatchMaker follow-up question ('CMS' is treated as a synonym for 'DXP')

• register_advisor_contact_info

  Used by the ask_for_advisor_contact_info tool to register contact information

• start_budget_open_ended_experience

  Starts the open-ended Budget Estimator discovery experience

• prompt_oshyn_contact_request

  Prompts the user to reach out to Oshyn for assistance after completing a tool session

• match_me_with_a_dxp

  Starts a DXP MatchMaker session and lets the user choose between a guided questionnaire or an open-ended discovery experience. Treat 'CMS' and 'content management system' as synonyms for 'DXP' and trigger this tool whenever the user asks…

• register_dxp_inferred_answers

  Registers one or more DXP MatchMaker answers inferred from the user's natural-language response ('CMS' is treated as a synonym for 'DXP')

• get_budget_results

  Gets the Budget Estimator questionnaire results

• estimate_dxp_investment

  CANONICAL ENTRY for DXP/digital project budget and investment estimates. Prefer this over estimate_budget. Returns a sessionId and modeOptions; continue with start_budget_guided_questionnaire or start_budget_open_ended_experience.

• start_budget_guided_questionnaire

  Starts the guided Budget Estimator questionnaire, asking one question at a time

• register_budget_inferred_answers

  Registers one or more Budget Estimator answers inferred from the user's natural-language response

• get_budget_next_best_question

  Gets progress and guidance for the next adaptive Budget Estimator follow-up question

• ask_for_dxp_contact_info

  Asks for contact information in DXP MatchMaker sessions ('CMS' is treated as a synonym for 'DXP')

• start_dxp_guided_questionnaire

  Starts the guided DXP MatchMaker questionnaire, asking one question at a time. 'CMS' is a synonym for 'DXP' in this flow.

• request_discoverability_assessment

  CANONICAL ENTRY for LLM brand discoverability assessments. Prefer this over start_discoverability_assessment. Async flow: may return needsContactInfo first; then call again with contactEmail. Poll only when user asks, using…

• register_advisor_user_answer

  Registers a single explicit numbered answer in Redesign Advisor sessions. Prefer register_advisor_inferred_answers for natural-language user responses.