Map messy columns to a known schema — 7 scorers, domain dictionaries, F1 0.84. Zero config.
Moved. This repo has moved into the monorepo at . This repo is archived; new development happens in the monorepo. Inference-driven schema mapping engine. Map messy source columns to a known target schema — accurately, explainably, with zero config. is a schema-mapping engine. Give it any two field collections (CSVs, DataFrames, database tables, in-memory records) and it figures out which source…
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 31 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Moved. This repo has moved into the monorepo at . This repo is archived; new development happens in the monorepo. Inference-driven schema mapping engine. Map messy source columns to a known target schema — accurately, explainably, with zero config. is a schema-mapping engine. Give it any two field collections (CSVs, DataFrames, database tables, in-memory records) and it figures out which source field corresponds to which target field, with confidence scores and human-readable reasoning.…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.