mcp-code-vector--search

The server design generally appears robust. It uses standard, reputable libraries (ChromaDB, Sentence Transformers). When run via Docker, it limits file system write access to only the index directory (`/vector-index`). Input validation for `query` and `filter_filepath` in `semantic_search` is handled by ChromaDB's query interface, reducing direct injection risks. No 'eval' or obvious hardcoded secrets are present. The communication for the MCP client interface occurs over standard I/O (`stdio_server`), which reduces the direct network attack surface. The primary risk would be if a malicious client (within a trusted environment) could craft highly inefficient queries leading to excessive resource consumption, but this is generally mitigated by running against your own codebase in a controlled environment.