liquidation-monitor — base web3 m2m hub MCP Tool
liquidation-monitor
(liquidation monitor) is one of 17 tools on the
base web3 m2m hub
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call liquidation-monitor from your client
- Claude Code base web3 m2m hub liquidation-monitor run in your project directory
- Claude Desktop base web3 m2m hub liquidation-monitor ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor base web3 m2m hub liquidation-monitor ~/.cursor/mcp.json
- VS Code base web3 m2m hub liquidation-monitor .vscode/mcp.json
- Zed base web3 m2m hub liquidation-monitor ~/.config/zed/settings.json
- Windsurf base web3 m2m hub liquidation-monitor ~/.codeium/windsurf/mcp_config.json
- Cline base web3 m2m hub liquidation-monitor ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI base web3 m2m hub liquidation-monitor ~/.gemini/settings.json
- Grok base web3 m2m hub liquidation-monitor .mcp.json (in your project root)
- ChatGPT base web3 m2m hub liquidation-monitor Settings → Connectors → Advanced → Developer mode
- Claude.ai base web3 m2m hub liquidation-monitor Settings → Connectors → Add custom connector
- LangChain base web3 m2m hub liquidation-monitor pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http base-web3-m2m-hub https://auditor-x402.onrender.com/mcp/v1Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 20 October 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.