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