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