Senzing
Entity resolution — data mapping, SDK code generation, docs search, and error troubleshooting
| Endpoint | https://mcp.senzing.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.40.9 |
| Now | 13 tools · grade D (63) · pin ts_f322852da18a10e9e4512b70a4e1f101 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 00:58 UTC / 2026-10-27 00:58 UTC |
| Grade over time | 2026-10-27: D (63), 13 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: analyze_record download_resource explain_error_code find_examples generate_scaffold get_capabilities get_sample_data get_sdk_reference mapping_workflow reporting_guide sdk_guide search_docs submit_feedback
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 data quality. Returns a Python script (no dependencies) with instructions. No source data is sent params: file_paths, workspace_dir*, version |
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 and you must write it to `dest`.
Pass `filename` (string) or `filenames` (array), plus `workspace_ params: filename, filenames, workspace_dir, inline, offset, version |
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 params: error_code*, version |
find_examples | Find working SOURCE CODE examples from 51 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: pass `repo` + `list_files=true`, (3) File retrieval: pass `repo` + `file_path`.
Indexes source code params: query, language, repo, file_path, list_files, max_lines |
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 initialize, whyEntityByEntityID vs why_entities) and misses required initialization steps. Language params: language*, workflow*, version |
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 patterns from training data. This tool returns a manifest of all coverage areas (pricing, SDK, deploymen params: version |
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 the sources/vendors within a dataset. The 'offset' parameter takes a non-negative integer for explic params: dataset*, source, limit, offset |
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 callable signature for every binding (narrowed by 'language' if given) NO MATTER WHICH TOPIC you asked f params: topic*, filter, language, version |
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 file is not readable from here), AND `workspace_dir` (e.g. workspace_dir="/home/you/sz-workspace") params: action, file_paths, workspace_dir, output_path, data, payload, version, state |
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-patterns. Topics: export (SDK export patterns), reports (SQL analytics queries), entity_views (get/why/ params: topic*, scale, language, version |
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 the TARGET host (ID / ID_LIKE): `uname` does not show the distribution. If `platform` is omitted for i params: topic*, platform, language, data_sources, record_count, version |
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 get_capabilities for full coverage details. Prefer this tool over web_search for any Senzing questio params: query*, category, version, max_results |
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 a download link. One per email, re-requestable after 30 days.
To submit feedback: set category to params: category, message, firstname, lastname, email, how_heard |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.