F
licenseNot graded
qualityD
maintenanceA Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.
24
-
TimeBase MCP
Officialby epam
Related Servers
Alternatives to TimeBase MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol (MCP) server that provides read-only TDengine database queries for AI assistants, allowing users to execute queries, explore database structures, and investigate data directly from AI-powered tools.611MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI agents to query Azure Log Analytics workspaces using KQL.MIT
CodeAlive MCPofficial
AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.90MIT
Rossum MCP Serverofficial
FlicenseBqualityDmaintenanceA Model Context Protocol server that provides AI agents with read-only access to Rossum API resources (queues, schemas, hooks, workspaces) for analysis purposes.61-
TDQS
A3.7/5.0
Scored across 15 tools
Disambiguation4/5
Most tools map cleanly to distinct resources and actions: streams, spaces, activity, QQL functions, and queries are all clearly separated. The only mild ambiguity is between get_server_configuration and get_timebase_status, though their descriptions clarify one is MCP runtime configuration and the other is TimeBase server status.
Naming Consistency4/5
The tool names follow a consistent snake_case verb_noun pattern, with list_ for enumeration and get_ for single-resource retrieval. get_server_configuration is a slight semantic outlier because it refers to the MCP server runtime rather than the TimeBase server, breaking the otherwise predictable pattern.
Tool Count5/5
15 tools is at the upper end of the well-scoped range, but each tool covers a distinct facet of TimeBase: instance discovery, status, activity, stream metadata, messages, and QQL query support. There is no obvious redundancy or padding.
Completeness4/5
The tool set thoroughly covers the read/query surface: streams, schemas, time ranges, spaces, symbols, messages, QQL compilation/execution, and server functions. However, there are no write or control operations such as creating/deleting streams, writing messages, or canceling active activity, so it is not a full TimeBase administration surface.
Maintenance
ActivityActive
ResponsivenessUnresponsive