report_broken_server — MCPExplorer MCP Tool
report_broken_server
(report broken server) is one of 14 tools on the
MCPExplorer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call report_broken_server from your client
- Claude Code MCPExplorer report_broken_server run in your project directory
- Claude Desktop MCPExplorer report_broken_server ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCPExplorer report_broken_server ~/.cursor/mcp.json
- VS Code MCPExplorer report_broken_server .vscode/mcp.json
- Zed MCPExplorer report_broken_server ~/.config/zed/settings.json
- Windsurf MCPExplorer report_broken_server ~/.codeium/windsurf/mcp_config.json
- Cline MCPExplorer report_broken_server ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCPExplorer report_broken_server ~/.gemini/settings.json
- Grok MCPExplorer report_broken_server .mcp.json (in your project root)
- ChatGPT MCPExplorer report_broken_server Settings → Connectors → Advanced → Developer mode
- Claude.ai MCPExplorer report_broken_server Settings → Connectors → Add custom connector
- LangChain MCPExplorer report_broken_server pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcpexplorer https://mcpexplorer.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.