Claudex

The evidence shows a non-root Docker user and a read-only mount for Claude project files, while PROJECT_ROOT can constrain the source directory; however, native operation scans potentially private conversations and writes a local database without finer directory, session, or field-level controls, so least_privilege is 2. Index rebuild, clearing, and export are explicit operations, and memory CRUD is exposed through named MCP tools, but no first-scan consent, sensitive-operation confirmation, or deletion safeguard is documented, so user_confirmation is 1. The README explains the source directory, SQLite index, ports, volumes, APIs, and exports, but not the complete retention lifecycle or network-exposure model, so data_flow_transparency is 2. There is no evidence of credential theft or covert exfiltration, but histories may contain secrets, source code, and personal data, while authentication, encryption, redaction, and secret filtering are not documented; sensitive_data_handling is therefore 1. Dependencies and runtime requirements are identified, but permissive ranges are used and the supplied evidence contains no lockfile, vulnerability scan, SBOM, or update policy, so dependency_security is 1. External effects are primarily local reads, database and memory writes, index clearing, and exports, and these are generally documented; the implications of binding the web service to 0.0.0.0 are not developed, so external_effects is 2. The index can be cleared or rebuilt and Docker can be stopped, but memory backups, transaction recovery, and recovery from accidental deletion are not documented, so rollback is 1. Repository, author, issue channel, and MIT copyright attribution are present, but the author email appears placeholder-like and publisher identity is unverified, so source_attribution is 2; unknown identity is not treated as suspicious.

The README, project tree, and package metadata are broadly consistent about the CLI, MCP binary, version line, and purpose, so self_consistency is 2; deductions reflect the README foregrounding 1.3.0 while package metadata says 1.3.4 and retaining older claude-viewer naming. Node.js 18+, npm, Claude Code history, ports, and installation paths are documented, and the checker is said to inspect dependencies, permissions, JSONL data, and database state, so dependency_availability is 2; no supplied lockfile or compatibility matrix establishes fully repeatable dependency resolution. Troubleshooting covers missing projects, broken search, ports, permissions, and dependencies with diagnostic commands, so failure_messages is 2; the evidence does not show structured errors from the MCP tools themselves.

Developers, QA engineers, and researchers are identified, with concrete browsing, search, analysis, export, and persistent-memory scenarios, justifying 3 for audience_and_scenarios. Features, APIs, MCP tool categories, prompts, indexing requirements, and roadmap boundaries are described, but the complete inputs, outputs, and prohibited behavior of each MCP tool are absent, so capability_boundaries is 2. Reindexing conditions and MCP setup are explicit, and operations appear to require deliberate MCP or API calls; specific per-tool trigger conditions and memory-write policy are not shown, so trigger_precision is 2. npm, source, Docker, custom ports, custom roots, Linux/macOS, and WSL2 paths are addressed, but native Windows behavior, Node/SQLite combinations, and non-Claude data sources are not established, so environment_fit is 2.

The README is thoroughly organized around quick start, configuration, architecture, formats, search, APIs, development, troubleshooting, and deployment, so information_architecture is 3. It gives actionable npm, npx, source, MCP, Docker, and production instructions, earning 3 for install_notes. CLI and package names are mostly stable, but legacy claude-viewer references and the 1.3.0 versus 1.3.4 presentation create minor drift, so naming_stability is 2. Search, API, Docker, parser-extension examples, and common-problem guidance are substantial, so examples_and_faq is 3. Manual reindexing, unfinished settings, and roadmap items are disclosed, but privacy, security, scale, concurrency, and MCP interoperability limits are not consolidated, so known_limitations is 2. The complete MIT text is supplied and agrees with package metadata, earning 3 for license. Dated release summaries and a full changelog path support 3 for versioning_changelog. The author, repository, Issues, Discussions, and contribution path are clear, but there is no maintenance team, support commitment, signed release path, or security-reporting channel, and publisher identity is unverified; maintenance_responsibility is 2.

The web UI supports conversation rendering, filtered search, analytics, and JSON/HTML/TXT exports, while MCP offers detail levels and structured memory, making the outputs directly usable and supporting 3 for output_usability. Unifying scattered Claude Code JSONL histories into a searchable web and MCP interface provides clear incremental value over manual inspection, so marginal_value is 3. The MIT license and local operation reduce acquisition cost, but installation across workspaces, index upkeep, SQLite storage, and privacy administration impose operational cost, and resource consumption is not quantified; cost_benefit is 2.

Many claims map to named directories, scripts, endpoints, binaries, and configuration, so claim_traceability is 2; stronger claims such as “enterprise-grade,” “121x faster,” and universal compatibility lack benchmarks, test results, or methodology in the supplied files. README and package metadata corroborate the product name, purpose, MCP executable, license, and version family, while LICENSE independently confirms MIT, so cross_source_corroboration is 2; only three files are supplied and no implementation, lockfile, or test contents provide broader corroboration. Marketing language is mixed with checkable facts, and performance and comprehensive-compatibility assertions are not clearly separated from demonstrated evidence, so fact_inference_separation is 1.