Inference-driven schema mapping engine — map messy source columns to a known target schema
About
Inference-driven schema mapping engine — map messy source columns to a known target schema
Security Report
The infermap MCP server is a well-structured schema mapping tool with appropriate authentication via environment variables (implicit MCP protocol), proper input validation, and secure error handling. Permissions match the server's purpose—file I/O for data processing and optional network access for database connections. Minor code quality observations around broad exception handling and logging of scorer breakdowns do not significantly impact security. Package verification found 1 issue (1 critical, 0 high severity).
5 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
How to Install & Connect
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
Getting Started
Once installed, try these example prompts and explore these capabilities:
- 1"Map the columns in my CRM export to our canonical customer schema"
- 2"What fields in this CSV match our warehouse table?"
- 3"Inspect the schema of my data file"
- 4"Apply the saved mapping to rename columns in my export"
- 5Tool: map — Map source columns to target schema using weighted scorer pipeline
- 6Tool: inspect — Show fields, types, samples, and statistics for a schema
- 7Tool: validate — Check that a source file satisfies a mapping config
- 8Tool: apply — Apply a saved mapping config to remap a file's columns
Documentation
View on GitHubFrom the project's GitHub README.
Moved. This repo has moved into the
benzsevern/goldenmatchmonorepo atpackages/python/infermap (and packages/typescript/infermap)/. This repo is archived; new development happens in the monorepo.
infermap 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. Available as a Python package on PyPI and a TypeScript package on npm, with mapping decisions verified bit-for-bit by a shared golden-test parity suite.
Table of contents
- Install
- Quick start
- How it works
- Features
- Which package should I use?
- Custom scorers
- CLI examples
- Config reference
- Documentation
- License
Install
Python
pip install infermap
Optional database extras:
pip install infermap[postgres] # psycopg2-binary
pip install infermap[mysql] # mysql-connector-python
pip install infermap[duckdb] # duckdb
pip install infermap[all] # all extras
TypeScript / Next.js
npm install infermap
Zero runtime dependencies in the core entrypoint. Compatible with Next.js Server Components, Route Handlers, Server Actions, and the Edge Runtime out of the box. See the package README for the full reference.
Quick start
Python
import infermap
# Map a CRM export CSV to a canonical customer schema
result = infermap.map("crm_export.csv", "canonical_customers.csv")
for m in result.mappings:
print(f"{m.source} -> {m.target} ({m.confidence:.0%})")
# fname -> first_name (97%)
# lname -> last_name (95%)
# email_addr -> email (91%)
# Apply mappings to rename DataFrame columns
import polars as pl
df = pl.read_csv("crm_export.csv")
renamed = result.apply(df)
# Save mappings to a reusable config file
result.to_config("my_mapping.yaml")
# Reload later — no re-inference needed
saved = infermap.from_config("my_mapping.yaml")
TypeScript
import { map } from "infermap";
const crm = [
{ fname: "John", lname: "Doe", email_addr: "j@d.co" },
{ fname: "Jane", lname: "Smith", email_addr: "j@s.co" },
];
const canonical = [
{ first_name: "", last_name: "", email: "" },
];
const result = map({ records: crm }, { records: canonical });
for (const m of result.mappings) {
console.log(`${m.source} → ${m.target} (${m.confidence.toFixed(2)})`);
}
// fname → first_name (0.44)
// lname → last_name (0.48)
// email_addr → email (0.69)
For Next.js, drop it directly into a Route Handler — works on Edge Runtime with zero config:
// app/api/infer/route.ts
import { map } from "infermap";
export const runtime = "edge";
export async function POST(req: Request) {
const { sourceCsv, targetCsv } = await req.json();
const result = map({ csvText: sourceCsv }, { csvText: targetCsv });
return Response.json(result);
}
How it works
Each field pair runs through a pipeline of 7 scorers. Each scorer returns a score in [0.0, 1.0] or abstains (None/null). The engine combines scores via weighted average (requiring at least 2 contributors), then uses the Hungarian algorithm for optimal one-to-one assignment.
| Scorer | Weight | What it detects |
|---|---|---|
| ExactScorer | 1.0 | Case-insensitive exact name match |
| AliasScorer | 0.95 | Known field aliases (fname ↔ first_name, tel ↔ phone) + domain dictionaries |
| InitialismScorer | 0.75 | Abbreviation-style names (assay_id ↔ ASSI, confidence_score ↔ CONSC) |
| PatternTypeScorer | 0.7 | Semantic type from sample values — email, date_iso, phone, uuid, url, zip, currency |
| ProfileScorer | 0.5 | Statistical profile similarity — dtype, null rate, unique rate, length, cardinality |
| FuzzyNameScorer | 0.4 | Jaro-Winkler similarity on normalized field names (with common-prefix canonicalization) |
| LLMScorer | 0.8 | Pluggable LLM-backed scorer (stubbed by default) |
The engine also applies common-prefix canonicalization — automatically stripping schema-wide prefixes like prospect_ so that City vs prospect_City is compared as City vs City. And optional confidence calibration transforms raw scores into calibrated probabilities post-assignment (ECE from 0.46 to 0.005 on real-world data).
Features
| Python | TypeScript | |
|---|---|---|
| 7 built-in scorers | ✅ | ✅ |
| Hungarian assignment | ✅ (scipy) | ✅ (vendored) |
| Custom scorers | @infermap.scorer | defineScorer() |
| Domain dictionaries | ✅ (YAML) | ✅ (inlined) |
| Confidence calibration | ✅ (Identity/Isotonic/Platt) | ✅ |
| Score matrix inspection | ✅ | ✅ |
| In-memory data | Polars, Pandas, list[dict] | Array<Record> |
| File providers | CSV, Parquet, XLSX | CSV, JSON |
| Schema definition files | YAML + JSON | JSON |
| Database providers | SQLite, Postgres, DuckDB | SQLite, Postgres, DuckDB |
| Engine config | YAML | JSON |
| Saved mapping format | YAML | JSON |
| CLI | ✅ (Typer) | ✅ (node:util) |
| Apply to DataFrame | ✅ | ❌ (CSV rewrite via CLI) |
| Edge-runtime compatible | ❌ | ✅ |
| Zero runtime deps | n/a | ✅ |
| Accuracy benchmark | ✅ (162 cases, F1 0.84) | ✅ (parity within 0.0005) |
Which package should I use?
| If you are… | Use |
|---|---|
| Building a Python data pipeline or notebook | Python |
| Building a Next.js app, Node service, or browser tool | TypeScript |
| Running mapping in a serverless edge function | TypeScript (zero Node built-ins) |
| Doing ad-hoc CSV exploration on the command line | Python CLI has more features; TS CLI is leaner |
| Both — Python backend + Next.js admin UI | Both — outputs are interoperable via the JSON config format |
What's new in v0.3
+18.3pp F1 on real-world data from four compounding improvements:
v0.2 baseline F1 0.657
+ min_conf 0.2 F1 0.765 (+10.8pp — empirically tuned threshold)
+ prefix-strip F1 0.821 (+5.6pp — City vs prospect_City now works)
+ InitialismScorer F1 0.840 (+1.9pp — ASSI, CONSC, RELATIT now work)
New features:
- Domain dictionaries —
MapEngine(domains=["healthcare"])loads curated aliases for your domain. Ships:generic(default),healthcare,finance,ecommerce. Seeexamples/09_domain_dictionaries.py. - Confidence calibration —
MapEngine(calibrator=cal)transforms raw scores into calibrated probabilities. Ships:IsotonicCalibrator,PlattCalibrator. Valentine ECE: 0.46 → 0.005. Seeexamples/10_calibration.py. - InitialismScorer — matches abbreviation-style column names (
assay_id ↔ ASSI). ChEMBL F1: 0.524 → 0.819. - Common-prefix canonicalization — automatically strips
prospect_,assays_, etc. before fuzzy matching. - Valentine corpus — 82 real-world schema-matching cases from the Valentine benchmark for accuracy testing.
- Full TypeScript parity — all new features ported. 186 TS tests. Benchmark F1 within 0.0005 of Python.
Custom scorers
Python
import infermap
from infermap.types import FieldInfo, ScorerResult
@infermap.scorer("prefix_scorer", weight=0.8)
def prefix_scorer(source: FieldInfo, target: FieldInfo) -> ScorerResult | None:
if source.name[:3].lower() != target.name[:3].lower():
return None
return ScorerResult(score=0.85, reasoning=f"Shared prefix '{source.name[:3]}'")
from infermap.engine import MapEngine
from infermap.scorers import default_scorers
engine = MapEngine(scorers=[*default_scorers(), prefix_scorer])
TypeScript
import { MapEngine, defaultScorers, defineScorer, makeScorerResult } from "infermap";
const prefixScorer = defineScorer(
"prefix_scorer",
(source, target) => {
if (source.name.slice(0, 3).toLowerCase() !== target.name.slice(0, 3).toLowerCase()) {
return null;
}
return makeScorerResult(0.85, `Shared prefix '${source.name.slice(0, 3)}'`);
},
0.8 // weight
);
const engine = new MapEngine({
scorers: [...defaultScorers(), prefixScorer],
});
CLI examples
The CLI works the same way in both packages:
# Map two files and print a report
infermap map crm_export.csv canonical_customers.csv
# Map and save the config (Python: --save, TS: -o)
infermap map crm_export.csv canonical_customers.csv -o mapping.json
# Apply a saved mapping to rename columns
infermap apply crm_export.csv --config mapping.json --output renamed.csv
# Inspect the schema of a file or DB table
infermap inspect crm_export.csv
infermap inspect "sqlite:///mydb.db" --table customers
# Validate a saved config against a source
infermap validate crm_export.csv --config mapping.json --required email,id --strict
Config reference
Both packages accept an engine config (scorer weight overrides + alias extensions). Python uses YAML, TypeScript uses JSON; the shape is identical.
# Python: infermap.yaml
domains:
- healthcare
- finance
scorers:
LLMScorer:
enabled: false
FuzzyNameScorer:
weight: 0.3
aliases:
order_id:
- order_num
- ord_no
// TypeScript: infermap.config.json
{
"scorers": {
"LLMScorer": { "enabled": false },
"FuzzyNameScorer": { "weight": 0.3 }
},
"aliases": {
"order_id": ["order_num", "ord_no"]
}
}
See infermap.yaml.example for a full annotated reference.
Documentation
- 📖 Wiki — full reference for both languages
- Getting Started
- Python API
- TypeScript API
- Python vs TypeScript — migration guide
- Scorers
- Architecture
- FAQ
- 🌐 Documentation site
- 🧪 Examples
- Python examples — 10 numbered scripts covering basic mapping, databases, custom scorers, config, domain dictionaries, calibration, and score-matrix introspection
- TypeScript examples — basic mapping, Next.js Edge Runtime, custom scorer, databases, domain dictionaries, save/reuse
- 📓 Open in Colab — Python notebook
- 💬 GitHub Discussions
- 🐛 Issue tracker
Author
License
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.