Skip to main content
Glama
safiyu

ctxtest

Related Servers

Alternatives to ctxtest

  • A
    license
    A
    quality
    A
    maintenance
    Local RAG system for Claude Code with hybrid search (semantic + BM25), cross-encoder reranking, markdown-aware chunking, and 12 MCP tools. Zero external servers, pure ONNX in-process.
    13
    415 PyPI
    278
    MIT

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    Cognitive prosthetic for AI agents. Indexes conversation history from ChatGPT, Claude Code, Cursor, and Gemini CLI into searchable embeddings. 25 MCP tools including tunnel_state (resume where you left off), switching_cost (quantify context-switch penalty), thinking_trajectory (track idea evolution), and alignment_check (decisions vs principles). LanceDB + Parquet, 12ms recall, local-first.
    25
    15 PyPI
    71
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Provides intelligent code context and analysis through semantic compression, AST parsing, and multi-language support. Offers 60-80% token reduction while enabling AI assistants to understand codebases through local analysis, OpenAI-enhanced insights, and GitHub repository integration.
    6
    16 npm
    3
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Provides persistent memory and a codebase knowledge graph for AI coding assistants, enabling shared context across multiple tools like Claude, Cursor, and ChatGPT, with significant token reduction.
    5
    13 npm
    MIT

TDQS

C2.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools, hello-world and stat, have completely distinct purposes with no overlap. An agent can easily distinguish between them without confusion.

Naming Consistency3/5

The naming conventions are not consistent: hello-world uses a hyphen and two words, while stat is a single word. This inconsistency could confuse an agent expecting a uniform pattern.

Tool Count2/5

With only 2 tools, the server feels very thin. For a server named ctxtest, more tools would be expected to provide meaningful functionality beyond a hello world and status check.

Completeness2/5

The tool surface is too sparse to infer a clear domain. There are obvious gaps: no tools for configuration, error handling, or any context-related operations that the server name might imply.

Maintenance

ActivityInactive
ResponsivenessResponsive