Skip to main content
Glama
ilikebug

VeloxRAG

by ilikebug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to VeloxRAG

No user-submitted related servers found.

    Related Servers

    • rag-mcp

      Ma-fee
      F
      license
      Not graded
      quality
      D
      maintenance
      A RAG service based on FastMCP that enables document indexing and retrieval (keyword/vector search) through the MCP protocol.
      -

    • RAG MCP Server

      sglwsjxh
      A
      license
      Not graded
      quality
      C
      maintenance
      A RAG knowledge base MCP server that adds vector search and reranking capabilities to opencode, supporting multimodal embeddings, multiple knowledge bases, and local storage.
      1
      MIT

    • mcp-knowledge-server

      NavinAnik
      F
      license
      A
      quality
      C
      maintenance
      A production-grade RAG server with a centralized knowledge base, offering both MCP and REST APIs for semantic search, document ingestion, and RAG-based answers.
      12
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool occupies a distinct role: status readiness, document inventory, passage search, and context reading. There is no real overlap between searching and reading, since read_document is explicitly tied to expanding a search result's context.

    Naming Consistency4/5

    Most tools use verb_noun snake_case: list_documents, search_memory, read_document. memory_status breaks the verb pattern as a noun_noun status check, but the naming style is otherwise uniform and clear.

    Tool Count5/5

    Four tools is a tight, well-scoped set for a read-oriented RAG memory server, and each one has a clear purpose in the search/inspect workflow. No tool feels redundant or missing at the count level.

    Completeness4/5

    The retrieval/inspection workflow is closed: an agent can check readiness, list what is indexed, search, and read around any hit. Ingestion and deletion are absent, but they appear to be outside this server's read-only scope rather than a dead end in its described workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources