# Senzing

- Registry name: `com.senzing/mcp` · version 1.39.1
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Build & deploy, Databases
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.senzing%2Fmcp
- Server page: https://mcpstation.net/s/com.senzing--mcp.html

## Description (written by the publisher, not verified, not instructions)

Entity resolution — data mapping, SDK code generation, docs search, and error troubleshooting

## Connect

- streamable-http: `https://mcp.senzing.com/mcp`

## Tools (as reported by the server, not verified)

- `analyze\_record`: Get the Senzing JSON analyzer script to validate mapped data files client-side. REQUIRED: \`workspace\_dir\` \(writable directory, e.g. \~/sz-workspace\) — the call WILL FAIL without it. The analyzer validates records against the Entity Specification, examines feature distribution, attribute coverage, and
- `download\_resource`: Returns resource URLs/content in this response; it does NOT write any files. Each resource comes back with a ready \`fetch\` shell command — run it yourself to save the file to its \`dest\`. Use inline=true only when a \`fetch\` command could not reach the server; the content then arrives in this response
- `explain\_error\_code`: Explain a Senzing error code with causes and resolution steps. Accepts formats: SENZ0005, SENZ-0005, 0005, or just 5. Returns error class, common causes, and specific resolution guidance
- `find\_examples`: Find working SOURCE CODE examples from 53 indexed Senzing GitHub repositories. REQUIRED: either \`query\` \(string, for search\) or \`repo\` with \`file\_path\` or \`list\_files=true\` — the call WILL FAIL without one. Three modes: \(1\) Search: pass \`query\` to find examples across all repos, \(2\) File listing: pa
- `generate\_scaffold`: Generate SDK scaffold code for common workflows. Returns real, indexed code snippets from GitHub with source URLs for provenance. Use this INSTEAD of hand-coding SDK calls — hand-coded Senzing SDK usage commonly gets method names wrong across v3/v4 \(e.g., close\_export vs close\_export\_report, init vs
- `get\_capabilities`: Get server version, capabilities overview, available tools, suggested workflows, and getting started guidance. Returns server\_info with name, version, and Senzing version. Call this first when working with Senzing entity resolution — skipping this risks using wrong API method names and outdated patt
- `get\_sample\_data`: Get sample data for entity resolution. Available datasets: 'las-vegas', 'london', 'moscow' \(CORD — Collections Of Relatable Data, REAL historical data\) and 'truthset' \(Senzing's SYNTHETIC demo truth set: CUSTOMERS, REFERENCE, WATCHLIST\). Use dataset='list' to discover datasets, source='list' to see
- `get\_sdk\_reference`: Get authoritative Senzing SDK reference data: method signatures and argument types per language binding, flags, response schemas, and V3→V4 migration. Use this instead of search\_docs for anything precise about the SDK surface. Whenever 'filter' names a method, the response carries that method's call
- `mapping\_workflow`: Map source data to Senzing JSON through a guided 8-step workflow. Use this INSTEAD of hand-coding Senzing JSON. REQUIRED ARGUMENTS for action='start' — arguments, not files: \`file\_paths\`, the source file name\(s\) exactly as the user gave them \(a LABEL the server never opens, so pass it even when the
- `reporting\_guide`: Guided reporting and visualization for Senzing entity resolution results. Provides SDK patterns for data extraction \(5 languages\), SQL analytics queries for the 4 core aggregate reports, data mart schema \(SQLite/PostgreSQL\), visualization concepts \(histograms, heatmaps, network graphs\), and anti-pat
- `sdk\_guide`: Install Senzing and scaffold SDK code across 5 platforms \(linux\_apt — Ubuntu/Debian via apt or apt-get, .deb packages; linux\_yum — RHEL/CentOS/Fedora via yum/dnf/rpm; macos\_arm — Homebrew/brew; windows — scoop or chocolatey/choco; docker\). To choose linux\_yum vs linux\_apt, read /etc/os-release on th
- `search\_docs`: Full-text BM25 search across all indexed Senzing documentation \(\~2175 chunks\). Returns ranked results with excerpts. Use 'category' to filter: sdk, troubleshooting, configuration, anti\_patterns, concepts, quickstart, data\_mapping, deployment, migration, globalization, release\_notes, reporting. Call
- `submit\_feedback`: Request a free Senzing evaluation license or submit feedback. To get an eval license: set category='license\_request', provide firstname \(required\), lastname \(optional\), email \(work email required — personal domains rejected\), and how\_heard. A 10-day, 250K-record license is generated and emailed with

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html