resource_track_record — crypto intelligence MCP Resource

resource_track_record is one of 2 resources on the crypto intelligence MCP server. Connect the server and your client can attach it as context.

by client

How to attach resource_track_record from your client

• Claude Code crypto intelligence Resource/resource_track_record run in your project directory
• Claude Desktop crypto intelligence Resource/resource_track_record ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor crypto intelligence Resource/resource_track_record ~/.cursor/mcp.json
• VS Code crypto intelligence Resource/resource_track_record .vscode/mcp.json
• Zed crypto intelligence Resource/resource_track_record ~/.config/zed/settings.json
• Windsurf crypto intelligence Resource/resource_track_record ~/.codeium/windsurf/mcp_config.json
• Cline crypto intelligence Resource/resource_track_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI crypto intelligence Resource/resource_track_record ~/.gemini/settings.json
• Grok crypto intelligence Resource/resource_track_record .mcp.json (in your project root)
• ChatGPT crypto intelligence Resource/resource_track_record Settings → Connectors → Advanced → Developer mode
• Claude.ai crypto intelligence Resource/resource_track_record Settings → Connectors → Add custom connector
• LangChain crypto intelligence Resource/resource_track_record pip install langchain-mcp-adapters

Other resources on this server

• list_endpoints

crypto intelligence also offers 3 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.