Home / MCP registry index / com.oshyn/mcp

Oshyn Free AI-Powered Website Tools

com.oshyn/mcp in the official MCP registry. Endpoint https://mcp.oshyn.com/.

The registry describes it as: Free AI-powered DXP tools by Oshyn: GEO & Reliability scan, Choose New DXP and Estimate DXP Budget.

We read its 40 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

start_advisor_guided_questionnaire start_discoverability_assessment start_dxp_open_ended_experience register_dxp_contact_info register_dxp_user_answer submit_oshyn_contact_request get_advisor_next_best_question ask_for_budget_contact_info start_advisor_open_ended_experience get_an_advice register_advisor_inferred_answers create_site_report estimate_budget request_reliability_report discoverability_assessment_status query_company_scores qualify_dxp_requirements get_advisor_results search_blog_with_keyword ask_for_advisor_contact_info register_budget_user_answer get_discoverability_assessment register_budget_contact_info get_dxp_results get_site_report_status get_dxp_next_best_question register_advisor_contact_info start_budget_open_ended_experience prompt_oshyn_contact_request match_me_with_a_dxp register_dxp_inferred_answers get_budget_results estimate_dxp_investment start_budget_guided_questionnaire register_budget_inferred_answers get_budget_next_best_question ask_for_dxp_contact_info start_dxp_guided_questionnaire request_discoverability_assessment register_advisor_user_answer

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-oshyn-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-oshyn-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.