list_paid_endpoints — GW8 Signal API MCP Tool Read-only
list_paid_endpoints
(list paid endpoints) is one of 17 tools on the
GW8 Signal API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_paid_endpoints from your client
- Claude Code GW8 Signal API list_paid_endpoints run in your project directory
- Claude Desktop GW8 Signal API list_paid_endpoints ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GW8 Signal API list_paid_endpoints ~/.cursor/mcp.json
- VS Code GW8 Signal API list_paid_endpoints .vscode/mcp.json
- Zed GW8 Signal API list_paid_endpoints ~/.config/zed/settings.json
- Windsurf GW8 Signal API list_paid_endpoints ~/.codeium/windsurf/mcp_config.json
- Cline GW8 Signal API list_paid_endpoints ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GW8 Signal API list_paid_endpoints ~/.gemini/settings.json
- Grok GW8 Signal API list_paid_endpoints .mcp.json (in your project root)
- ChatGPT GW8 Signal API list_paid_endpoints Settings → Connectors → Advanced → Developer mode
- Claude.ai GW8 Signal API list_paid_endpoints Settings → Connectors → Add custom connector
- LangChain GW8 Signal API list_paid_endpoints pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gw8-signal-api https://micro-saas-agent.onrender.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 18 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.