check_mcp_server — MCP Surface Lint MCP Tool Read-only
check_mcp_server
(check mcp server) is one of 1 tool on the
MCP Surface Lint
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_mcp_server from your client
- Claude Code MCP Surface Lint check_mcp_server run in your project directory
- Claude Desktop MCP Surface Lint check_mcp_server ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCP Surface Lint check_mcp_server ~/.cursor/mcp.json
- VS Code MCP Surface Lint check_mcp_server .vscode/mcp.json
- Zed MCP Surface Lint check_mcp_server ~/.config/zed/settings.json
- Windsurf MCP Surface Lint check_mcp_server ~/.codeium/windsurf/mcp_config.json
- Cline MCP Surface Lint check_mcp_server ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCP Surface Lint check_mcp_server ~/.gemini/settings.json
- Grok MCP Surface Lint check_mcp_server .mcp.json (in your project root)
- ChatGPT MCP Surface Lint check_mcp_server Settings → Connectors → Advanced → Developer mode
- Claude.ai MCP Surface Lint check_mcp_server Settings → Connectors → Add custom connector
- LangChain MCP Surface Lint check_mcp_server pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-surface-lint https://mcplint-web.vercel.app/api/mcp
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.