Since
Related Servers
Alternatives to Since
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceReduces token consumption for AI coding agents by 50-70% through intelligent code context filtering, Git delta tracking, and local SQLite/Tree-sitter indexing.167 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a unified context layer for Cursor's agent with lossless token savings and verifiable memory, enabling efficient code exploration and cross-session continuity.4 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, explore data lineage, understand business context, and generate SQL queries across an organization's data ecosystem.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceTransforms static coding standards into a queryable live data store for AI agents, delivering task-specific rules and fix guidance on demand. This optimizes context window usage through progressive disclosure, ensuring agents apply relevant governance without loading massive documentation.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to query a persistent local code graph for targeted context, blast-radius analysis, and incremental updates, so they read only relevant files during reviews and large-repo workflows.MIT
- AlicenseBqualityBmaintenanceProvides a shared context layer for AI agent teams to improve token efficiency through context deduplication and incremental state sharing. It enables multiple agents to coordinate tasks, share real-time discoveries, and manage dependencies while significantly reducing redundant data transmission.1508MIT
TDQS
Scored across 4 tools
Each tool has a distinct role in the workflow: since() produces a digest, get() retrieves details from handles, ack() advances the cursor, and status() reports source health. The descriptions clearly delineate boundaries, and the complementary read-then-ack pattern prevents confusion.
All names are single lowercase words, which is readable, but they mix parts of speech: since is a preposition, get and ack are verbs, and status is a noun. There is no consistent verb_noun or action-oriented pattern.
Four tools perfectly match the narrow purpose of tracking changes: read digest, drill into details, acknowledge, and check health. Each tool is necessary and there is no redundancy or bloat.
The surface covers the full lifecycle: discovering changes (since), inspecting them (get), marking them handled (ack), and monitoring source health (status). No CRUD operations are needed for this read-only monitoring domain, so there are no obvious gaps.