Drata MCP Server
Related Servers
Alternatives to Drata MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects Claude to Clio practice management, enabling AI-assisted access to matters, contacts, documents, tasks, and billing with audit logging and encryption for law firm compliance.440 npm27MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude to OCI Logging Analytics for natural language querying and analysis of security logs, including detection catalog, MITRE ATT&CK integration, and cross-log correlation.2MIT
- AlicenseNot gradedqualityNot gradedmaintenanceConnects Claude AI to Google Search Console with OAuth 2.0 authentication, enabling users to analyze search performance, inspect URLs, manage sitemaps, and export analytics data through natural language conversations.2-
- AlicenseNot gradedqualityDmaintenanceConnects Claude Code to any ObjectStack deployment, enabling discovery, querying, and updating of objects and records, plus running business actions, all under user permissions and row-level security.Apache 2.0
- AlicenseAqualityDmaintenanceConnects Claude to Amazon Seller Central via the SP-API for natural language queries on sales, inventory, reports, fees, reimbursements, and analytics.2049MIT
- FlicenseAqualityCmaintenanceConnects Claude to your Amazon Seller Central account via the Selling Partner API, enabling queries for recent orders, sales summaries, FBA inventory, and financial events.4-
TDQS
Scored across 21 tools
Tools are mostly distinct by resource, but list_controls_with_issues and list_failing_monitors duplicate functionality already available via filters on list_controls and list_monitors, creating overlap. Descriptions attempt to guide usage, but an agent may still struggle to choose the right tool for issue-focused queries.
Almost all tools follow a snake_case verb_noun pattern (list_* for collections, get_* for details). Minor deviation: get_monitors_for_control uses get_ for a list operation, and some list_* names include qualifiers, but the convention is predictable.
21 tools is at the upper end of reasonable for a compliance platform covering many resource types. However, the count is inflated by redundant issue-specific aliases, making the set feel heavier than necessary.
The server covers major compliance entities and includes detail endpoints for controls, monitors, and personnel. Yet many resources (policies, vendors, devices, evidence, assets, users) are list-only, and no mutation tools exist, leaving notable gaps for deeper investigation or remediation workflows.