rubric-tdqs — AgentDiet DEX Liquidity, Slippage & Orderflow Audit API MCP Resource
rubric-tdqs
is one of 10 resources on the
AgentDiet DEX Liquidity, Slippage & Orderflow Audit API
MCP server. Connect the server and your client can attach it as context.
by client
How to attach rubric-tdqs from your client
- Claude Code AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs run in your project directory
- Claude Desktop AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs ~/.cursor/mcp.json
- VS Code AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs .vscode/mcp.json
- Zed AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs ~/.config/zed/settings.json
- Windsurf AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs ~/.codeium/windsurf/mcp_config.json
- Cline AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs ~/.gemini/settings.json
- Grok AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs .mcp.json (in your project root)
- ChatGPT AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs Settings → Connectors → Add custom connector
- LangChain AgentDiet DEX Liquidity, Slippage & Orderflow Audit API Resource/rubric-tdqs pip install langchain-mcp-adapters
Other resources on this server
AgentDiet DEX Liquidity, Slippage & Orderflow Audit API also offers 2 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 19 October 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.