get_eviduct_network_status — Eviduct Trust Firewall MCP Tool Read-only
get_eviduct_network_status
(get eviduct network status) is one of 3 tools on the
Eviduct Trust Firewall
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_eviduct_network_status from your client
- Claude Code Eviduct Trust Firewall get_eviduct_network_status run in your project directory
- Claude Desktop Eviduct Trust Firewall get_eviduct_network_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Eviduct Trust Firewall get_eviduct_network_status ~/.cursor/mcp.json
- VS Code Eviduct Trust Firewall get_eviduct_network_status .vscode/mcp.json
- Zed Eviduct Trust Firewall get_eviduct_network_status ~/.config/zed/settings.json
- Windsurf Eviduct Trust Firewall get_eviduct_network_status ~/.codeium/windsurf/mcp_config.json
- Cline Eviduct Trust Firewall get_eviduct_network_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Eviduct Trust Firewall get_eviduct_network_status ~/.gemini/settings.json
- Grok Eviduct Trust Firewall get_eviduct_network_status .mcp.json (in your project root)
- ChatGPT Eviduct Trust Firewall get_eviduct_network_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Eviduct Trust Firewall get_eviduct_network_status Settings → Connectors → Add custom connector
- LangChain Eviduct Trust Firewall get_eviduct_network_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http eviduct https://eviduct-mvp.onrender.com/mcp/gatewayOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.