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