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