rubric-tdqs — AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor MCP Resource
rubric-tdqs
is one of 10 resources on the
AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor
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 A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs run in your project directory
- Claude Desktop AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs ~/.cursor/mcp.json
- VS Code AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs .vscode/mcp.json
- Zed AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs ~/.config/zed/settings.json
- Windsurf AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs ~/.codeium/windsurf/mcp_config.json
- Cline AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs ~/.gemini/settings.json
- Grok AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs .mcp.json (in your project root)
- ChatGPT AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs Settings → Connectors → Add custom connector
- LangChain AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor Resource/rubric-tdqs pip install langchain-mcp-adapters
Other resources on this server
AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor 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.