mcp-yearning
Related Servers
Alternatives to mcp-yearning
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Yearning SQL review platform, enabling read-only queries, ticket management (submit, audit, undo, rollback), query applications, comments, and data source/table exploration via REST/WebSocket APIs.198 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server for MySQL database integration with AI agents, enabling database exploration, CRUD operations, schema management, and performance monitoring through natural language.744 npmMIT
- AlicenseNot gradedqualityDmaintenanceA MySQL MCP server for secure database interaction, enabling schema inspection, query execution, and RBAC via AI coding assistants.1,352 npm5MIT
- AlicenseNot gradedqualityDmaintenanceProduction-ready MCP server for MySQL databases enabling AI assistants to interact with MySQL through secure, validated, and audited tools.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to MySQL databases for schema exploration, data querying, and SQL execution via natural language.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query company logs, databases, caches, and config centers (e.g., Aliyun SLS, MySQL, Redis, Nacos) through local MCP servers, with read-only enforcement and SSH tunneling for production access.-
TDQS
Scored across 14 tools
Each tool targets a distinct resource and action: user info, source listing, database/table/field metadata, SQL check, order retrieval (my orders, audit orders), order details (detail, timeline, rollback, comments), and query execution. The two order-listing tools (my_orders vs audit_orders) are clearly differentiated by user vs auditor perspective.
All tools share the 'yearning_' prefix and use snake_case. Most follow a verb_noun pattern (list_sources, list_tables, run_query) while some are noun-based (table_fields, order_detail). This is a minor deviation but overall predictable and readable.
14 tools is well within the typical range for a domain-specific server. The count matches the platform's complexity and each tool covers a distinct aspect of the SQL audit and query workflow.
The tools heavily favor read/query operations but lack critical actions. The description in yearning_sql_check references a 'submit_order' tool that is absent, so the core workflow of submitting SQL for approval is incomplete. Additionally, there is no tool for approving/rejecting orders from the auditor perspective, only listing them. This leaves significant functional gaps.