get_vendor_status — Merlonix Monitoring MCP Tool Read-only
get_vendor_status
(get vendor status) 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 get_vendor_status from your client
- Claude Code Merlonix Monitoring get_vendor_status run in your project directory
- Claude Desktop Merlonix Monitoring get_vendor_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Merlonix Monitoring get_vendor_status ~/.cursor/mcp.json
- VS Code Merlonix Monitoring get_vendor_status .vscode/mcp.json
- Zed Merlonix Monitoring get_vendor_status ~/.config/zed/settings.json
- Windsurf Merlonix Monitoring get_vendor_status ~/.codeium/windsurf/mcp_config.json
- Cline Merlonix Monitoring get_vendor_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Merlonix Monitoring get_vendor_status ~/.gemini/settings.json
- Grok Merlonix Monitoring get_vendor_status .mcp.json (in your project root)
- ChatGPT Merlonix Monitoring get_vendor_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Merlonix Monitoring get_vendor_status Settings → Connectors → Add custom connector
- LangChain Merlonix Monitoring get_vendor_status 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.