library-enrichment

A local-first library-evidence service for Rust and Python, exposed over MCP.

It answers the question a package index cannot: given a design objective and a concrete dependency environment, what relevant library capabilities exist, what evidence supports their use, what configuration do they require, and what remains unverified?

The service produces evidence. The calling agent produces judgments. It complements Context7 — Context7 explains concepts, this service establishes exact-release facts about the dependencies a project actually resolved.

Status

Phase 0 of 6. See STATUS.md for the current gate tally and docs/reports/acceptance.md for per-gate results. This repository is under active construction; the governing specification is complete and frozen, the implementation is not.

Related MCP server: RTFD (Read The F*****g Docs)

What it does

Nine MCP tools over a shared evidence core:

Evidence carries provenance: every material fact traces to an exact artifact, a producer run, and a recorded environment. Declared availability, configured availability, type-check success, and runtime behavior are separate states — the service never collapses them.

Architecture

A Rust daemon owns identity, resolution, fetching, normalization, evidence storage, querying, job state, policy, and publication. Evidence lands in immutable Arrow/Parquet snapshots queried through DataFusion. A thin FastMCP 4 adapter exposes the tools; a separate worker runs Griffe extraction and isolated runtime probes.

coding agent ──┬── Context7 MCP ─────────► concepts, documentation examples
               │
               ├── library-research skill ► routing, evidence policy, synthesis
               │
               └── FastMCP 4 stdio adapter
                            │ typed, bounded local RPC
                            ▼
                   library-enrichmentd ──► fetchers, Rust/Python API producers,
                            │              LSP sessions, sandboxed verification
                            ▼
                   immutable evidence snapshots (Arrow/Parquet + DataFusion)

Service code, tool environments, extraction workspaces, caches, and outputs live outside every working repository. The repository under study is never a subprocess working directory, an extraction destination, or an install target.

Documentation

Development

just --list        # every recipe
just doctor        # verify the toolchain and required producers are present
just ci            # gates for completed phases, plus the next one

Requires a pinned stable Rust toolchain (rust-toolchain.toml), uv, and just. Build and runtime verification profiles additionally require a working container runtime or bwrap.

License

Dual-licensed under either MIT or Apache-2.0, at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.