conda-meta-mcp

The project explicitly states a "Side-effect free by contract" design, with "No environment mutation" and "No external command side effects." Code review confirms adherence to this model, with no 'eval', 'exec', or direct file system writes for data storage beyond internal caching. It uses `requests.get` for `file_path_search` and `conda`'s internal mechanisms for `package_search` and `repoquery`, which involve legitimate network requests to fetch package metadata. All external I/O operations are wrapped in `asyncio.to_thread` for non-blocking execution, and `lru_cache` is used extensively to optimize performance and reduce repeated external calls. Input validation is present for many tools (e.g., `import_mapping`, `pypi_to_conda`, `file_path_search`) to prevent malformed queries.