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