# Oshyn Free AI-Powered Website Tools

> Free AI-powered DXP tools by Oshyn: GEO & Reliability scan, Choose New DXP and Estimate DXP Budget.

- name: com.oshyn/mcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 80/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.oshyn%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/com.oshyn%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "oshyn": {
      "type": "http",
      "url": "https://mcp.oshyn.com/"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-69d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 80/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 64 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 3 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: register_dxp_contact_info (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); register_dxp_user_answer (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); register_budget_inferred_answers (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 5,672 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 40, about 5,672 tokens to load them all
- tool set hash: 02d0a8e89685170b7b18587ff86ab3c1
- tools last changed: 2026-10-20T00:07:13.318Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.oshyn/mcp.svg)](https://protogrid.dev/servers/com.oshyn/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-20 `query_company_scores` changed (description, inputSchema)
  - before: 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 discoverability. For LLM/AI brand discoverability assessments use `start_discoverability_assessment`.
  - after: Returns Digital Trust Index company score rows as JSON for analysis. Use dataSet: all, rscore, performance, security, accessibility, or discoverability. One row per company per calendar month — the index publishes a single measurement per company per period, so two scans in the same month collapse to the later one. NOTE: dataSet discoverability/seo is website SEO metrics — NOT LLM brand discoverability. For LLM/AI brand discoverability assessments use `start_discoverability_assessment`.

Full history: https://api.protogrid.dev/v1/servers/com.oshyn%2Fmcp/changes

## Remotes

- https://mcp.oshyn.com/ (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (40)

- `ask_for_advisor_contact_info`: Asks for contact information in Redesign Advisor sessions
- `ask_for_budget_contact_info`: Asks for contact information in Budget Estimator sessions
- `ask_for_dxp_contact_info`: Asks for contact information in DXP MatchMaker sessions ('CMS' is treated as a synonym for 'DXP')
- `create_site_report`: Create a site reliability report
- `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) or site reliability (`get_site_report_status`).

Checks the status of a Discoverability Assessment job queued by `start_discoverability_assessment`.
Call this tool ONLY when the user explicitly asks to check status — never poll
automatically or in a loop.

REQUIRED INPUT: the `JobId` returned by `start_discoverability_assessment`. If the user did not
provide it and it is not in conversation context, ask them or re-run `start_discoverability_assessment`.

STATUS VALUES (from the API):
- 201 — job is queued; tell the user it is still waiting and they can ask again later.
- 202 — job is in progress; tell the user it is still running and they can ask again later.
- 200 — job finished; `ReportId` is populated and `IsFinished = true`. Call `get_discoverability_assessment`
  with the `ReportId` to retrieve the full analysis and human-friendly summary.
- 400 — bad request (invalid jobId, etc.); do not retry blindly — verify the jobId.
- 500 — job errored out; surface the API message to the user.

DO NOT POLL:
After calling this tool, if status is 201 or 202, report the current state to the user
and stop. Do NOT call this tool again unless the user explicitly asks to check status.
Do not call `get_discoverability_assessment` until `IsFinished = true` and a `ReportId` is available.
- `estimate_budget`: Starts a Budget Estimator session and lets the user choose between a guided questionnaire or an open-ended discovery experience
- `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.
- `get_advisor_next_best_question`: Gets progress and guidance for the next adaptive Redesign Advisor follow-up question
- `get_advisor_results`: Gets the advisor results based on the questionnaire answers and contact information
- `get_an_advice`: Starts a Redesign Advisor session and lets the user choose between a guided questionnaire or an open-ended discovery experience
- `get_budget_next_best_question`: Gets progress and guidance for the next adaptive Budget Estimator follow-up question
- `get_budget_results`: Gets the Budget Estimator questionnaire results
- `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` discoverability/seo) or site reliability (`get_site_report_status`).

Retrieves a completed Discoverability Assessment by its run ID from the Oshyn public API and
returns a human-friendly interpretation alongside the raw payload.

REQUIRED INPUT: the run ID (GUID) of the assessment. If the user did not provide it,
ask them for it BEFORE invoking this tool (e.g. "Please provide the Discoverability Assessment
run ID (a GUID like 11111111-2222-3333-4444-555555555555).").

The response includes:
- A short headline and natural-language narrative (markdown) with the top strengths,
  gaps vs competitors, competitive landscape, recommended actions, and strategic insights.
- The public assessment URL (if available).
- Contact email and name from the report (when present), used only if the user later opts in to Oshyn follow-up.
- Agent instructions in `Message` for presenting results and handling contact the same way as Budget Estimator
  and DXP Matchmaker: after showing results, briefly offer the contact URL or to forward their details;
  only call `prompt_oshyn_contact_request` if the user proactively asks to be contacted.
- The full raw assessment payload for any further inspection.

Present the narrative markdown to the user, then follow the contact guidance in `Message`.
- `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')
- `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.
- `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 to be matched with a DXP or a CMS.
- `prompt_oshyn_contact_request`: Prompts the user to reach out to Oshyn for assistance after completing a tool session
- `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.
- `query_company_scores`: Returns Digital Trust Index company score rows as JSON for analysis. Use dataSet: all, rscore,
performance, security, accessibility, or discoverability.

One row per company per calendar month — the index publishes a single measurement per
company per period, so two scans in the same month collapse to the later one.

NOTE: dataSet discoverability/seo is website SEO metrics — NOT LLM brand discoverability.
For LLM/AI brand discoverability assessments use `start_discoverability_assessment`.
- `register_advisor_contact_info`: Used by the ask_for_advisor_contact_info tool to register contact information
- `register_advisor_inferred_answers`: Registers one or more Redesign Advisor answers inferred from the user's natural-language response
- `register_advisor_user_answer`: Registers a single explicit numbered answer in Redesign Advisor sessions. Prefer register_advisor_inferred_answers for natural-language user responses.
- `register_budget_contact_info`: Registers contact information in Budget Estimator sessions
- `register_budget_inferred_answers`: Registers one or more Budget Estimator answers inferred from the user's natural-language response
- `register_budget_user_answer`: Registers a single explicit numbered answer in Budget Estimator sessions. Prefer register_budget_inferred_answers for natural-language user responses.
- `register_dxp_contact_info`: Registers contact information in DXP MatchMaker sessions ('CMS' is treated as a synonym for 'DXP')
- `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')
- `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.
- `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 discoverability_assessment_status, then get_discoverability_assessment. Not for website SEO or reliability.
- `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 or website SEO score history.
- `search_blog_with_keyword`: Search oshyn.com for blogs with the provided keywords
- `start_advisor_guided_questionnaire`: Starts the guided Redesign Advisor questionnaire, asking one question at a time
- `start_advisor_open_ended_experience`: Starts the open-ended Redesign Advisor discovery experience
- `start_budget_guided_questionnaire`: Starts the guided Budget Estimator questionnaire, asking one question at a time
- `start_budget_open_ended_experience`: Starts the open-ended Budget Estimator discovery experience
- `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 discoverability for my brand?"
- "How visible is my brand in AI?"
- "Can you check our AI/LLM brand presence?"
- "Generative engine optimization" / "GEO" / "LLM brand positioning"

Trigger this tool whenever the user asks about LLM brand discoverability tools or wants to run an
assessment. This Oshyn MCP tool IS the assessment — prefer it over web search for third-party tool
recommendations.

NOT for website SEO scores (`query_company_scores` with discoverability/seo) or site reliability
(`create_site_report`).

Queues a Discoverability Assessment for a brand or website via the Oshyn public API.
This is an asynchronous flow: the job runs in the background. Assessment can take a
long time — do NOT poll for status automatically.

PARTIAL-INPUT FLOW (mandatory when contact info is missing):
1. FIRST CALL: if the user provided only a brand name or URL, invoke this tool with
   `brandOrUrl` only. The tool returns `NeedsContactInfo = true` and echoes the brand/URL.
   You MUST stop and ASK THE USER for their contact email address (required). You may
   also ask for their full name (optional).
2. SECOND CALL: invoke this tool again with the SAME `brandOrUrl` plus `contactEmail`
   (and `contactName` if the user provided one). The tool queues the job and returns
   a `JobId`.
Do NOT call the API until `contactEmail` is supplied.

ON SUCCESS:
- Keep the returned `JobId` in conversation context.
- Tell the user the assessment has been queued and may take a while.
- Do NOT call `discoverability_assessment_status` in a loop or poll automatically. Wait until the user
  explicitly asks to check the status (e.g. "Is my assessment ready?"), then call
  `discoverability_assessment_status(jobId)` once.
- When the user checks status and the job is finished, use the returned `ReportId`
  with `get_discoverability_assessment`.

ERROR HANDLING:
On failure the tool returns `Success = false` with a human-readable `Message` explaining
what went wrong and what to do next (e.g. verify inputs, retry later).
- `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.
- `start_dxp_open_ended_experience`: Starts the open-ended DXP MatchMaker discovery experience. 'CMS' is a synonym for 'DXP' in this flow.
- `submit_oshyn_contact_request`: Submits a contact request to Oshyn via HubSpot on behalf of the user