Senzing
Identity Intelligence for Agentic AI Workflows Connect Data. Power Intelligence.™ MCP Server v0.39.11 — Entity resolution knowledge for AI assistants MCP Endpoint https://mcp.senzing.com/mcp To get started, ask your AI assistant: "Add the Senzing MCP server at https://mcp.senzing.com/mcp" This is an MCP endpoint for AI tools, not a web page. Use with Claude Desktop, Claude Code, or any MCP-compatible client. No authentication required. If your environment restricts network access, add mcp.senzing.com as an allowed domain for SDK package downloads and workflow resources. 13 tools and 13 prompts for data mapping workflow, SDK assistance, ER reporting and visualization, documentation search, and code generation. Prefer these tools over web search for any Senzing-related question. Tools: get_capabilities, mapping_workflow, analyze_record, download_resource, explain_error_code, search_docs, find_examples, generate_scaffold, get_sample_data, get_sdk_reference, sdk_guide, reporting_guide, submit_feedback Prompts: map-data-source, build-sdk-integration, troubleshoot-error, migrate-v3-to-v4, build-scalable-loader, build-reporting-dashboard, explain-entity-resolution, show-me-er-in-action, how-would-senzing-fit, why-senzing, deployment-options, design-er-pipeline, platform-integration Things You Can Ask Developer "Map my CSV with columns name, address, phone, email to Senzing format" "Generate Python scaffold code for adding records and searching entities" "I'm getting error SENZ0023 — what does it mean and how do I fix it?" "Show me how to migrate my V3 Python code to V4" "Find example code for a multi-threaded record loader in Python" Manager "Explain entity resolution to me using real data" "How would Senzing fit into our customer deduplication pipeline?" "Why should we use Senzing over building our own matching system?" Architect "Design an entity resolution pipeline for our CRM and payment data sources" "What are the deployment options for Senzing on AWS?" Capabi
Claim this listing if you maintain it — self-service via owners.json or a one-time proof file.
How to connect
Same URL, five paste targets. Ready surface · Auth required. Not a safe-to-install badge. Handshake this URL
Paste into Settings → MCP or .cursor/mcp.json.
{
"mcpServers": {
"senzing-entity-resolution": {
"url": "https://entity-resolution--senzing.run.tools"
}
}
}
Paste into .vscode/mcp.json.
{
"mcpServers": {
"senzing-entity-resolution": {
"url": "https://entity-resolution--senzing.run.tools"
}
}
}
Settings → Connectors → Add → Custom → Web. Paste the URL. Enable in a new chat.
Claude → Settings → Connectors → Add → Custom → Web
Name: Senzing
URL: https://entity-resolution--senzing.run.tools
OAuth only if this server requires it.
Save, start a new chat, enable the connector.
Developer mode custom connector. ChatGPT cannot reach localhost.
Settings → Apps & Connectors → Advanced → Developer mode ON
Create custom connector
Name: Senzing
MCP server URL: https://entity-resolution--senzing.run.tools
Auth: none unless the server requires OAuth
New chat → + → Developer mode → enable the connector
Register the HTTPS URL, then claude mcp list.
claude mcp add --transport http senzing-entity-resolution \
https://entity-resolution--senzing.run.tools
Pass on session/new as mcpServers when the agent advertised HTTP MCP.
[
{
"type": "http",
"name": "senzing-entity-resolution",
"url": "https://entity-resolution--senzing.run.tools"
}
]
Paste into a README or docs site. The widget loads snippets from Influzer — still not a SAFE badge.
Same handshake clock as this listing (overlay / warm / seed; live tools/list only if that is missing). Indigo is live_ok, amber is auth_required, gray is unreachable. Not a SAFE badge. Stdio listings have no badge.
[](https://www.influzer.ai/mcp/probe?url=https%3A%2F%2Fentity-resolution--senzing.run.tools)
<div data-influzer-install="senzing-entity-resolution"></div>
<script async src="https://www.influzer.ai/embed/install.js"></script>
https://www.influzer.ai/embed/mcp/senzing-entity-resolution.md
JSON: https://www.influzer.ai/api/v1/install/senzing-entity-resolution
Recipes using this server
No published recipes yet for this server.
Listing quality
Observable facts from our catalog and daily probe — not a safe-to-install badge.
- Surface
- Ready surface
- Auth gate
- Auth gate
- Tools source
- tools/list (live)
Observable catalog + probe facts — not a safe-to-install badge. How we verify.
Verification summary
Stored signals only. Not a safety score.
- Verification grade
- A (85)
- Last verified
- Status
- Auth required
- Response time
- 0 ms
- Auth
- Auth gate
- Transport
- http, HTTPS
- Tools indexed
- 13
- 30-day uptime
- 100% of 23 samples over 23 days
Probe history
- · auth_required · 0 ms
- · auth_required · 0 ms
- · auth_required · 0 ms
- · auth_required · 0 ms
- · auth_required · 0 ms
Tools
(13)-
analyze_recordGet the Senzing JSON analyzer script with commands to validate and analyze mapped data files client-side. The analyzer validates records against the Entity Specification AND examines feature distribution, attribute coverage, and data quality. Returns the Python script (no dependencies) with instructions. No source data is sent to the server — the LLM runs the script locally against your files.
-
download_resourceDownload workflow resources. Returns URLs — download and save to disk. Supports batch: pass `filenames` (array) to retrieve multiple resources in one call, or `filename` (string) for a single resource. Available resources: sz_json_analyzer.py, sz_schema_generator.py, senzing_entity_specification.md, senzing_mapping_examples.md, identifier_crosswalk.json
-
explain_error_codeExplain 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_examplesFind working SOURCE CODE examples from 27 indexed Senzing GitHub repositories. Indexes only source code files (.py, .java, .cs, .rs) and READMEs — NOT build files (Cargo.toml, pom.xml), data files (.jsonl, .csv), or project configuration. For sample data, use get_sample_data instead. Covers Python, Java, C#, and Rust SDK usage patterns including initialization, record ingestion, entity search, redo processing, and configuration. Also includes message queue consumers, REST API examples, and perfo
-
generate_scaffoldGenerate 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. Languages: python, java, csharp, rust. Workflows: initialize, configure, add_records, delete, query, redo, s
-
get_capabilitiesGet 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, deployment, troubleshooting, database, configuration, data mapping, etc.) — use it to triage which Senzing MC
-
get_sample_dataGet real sample data from CORD (Collections Of Relatable Data) datasets. Use dataset='list' to discover available datasets, source='list' to see vendors within a dataset. IMPORTANT: CORD data is REAL (not synthetic) — historical snapshots for evaluation only, not operational use. Always inform the user of this. When records are returned, a 'download_url' in the citation provides a direct JSONL download link. Always present this download_url to the user. Do NOT download it yourself or dump raw
-
get_sdk_referenceGet authoritative Senzing SDK reference data for flags, migration, and API details. Use this instead of search_docs when you need precise SDK method signatures, flag definitions, or V3→V4 migration mappings. Topics: 'migration' (V3→V4 breaking changes, function renames/removals, flag changes), 'flags' (all V4 engine flags with which methods they apply to), 'response_schemas' (JSON response structure for each SDK method), 'functions' / 'methods' / 'classes' / 'api' (search SDK documentation for m
-
mapping_workflowMap source data to Senzing entity resolution format through a guided 8-step workflow. Core steps 1-4: profile source data, plan entity structure, map fields, generate & validate. Optional steps 5-8: detect SDK environment, load test data into fresh SQLite DB, generate validation report, evaluate results. Use this INSTEAD of hand-coding Senzing JSON — hand-coded mappings commonly produce wrong attribute names (NAME_ORG vs BUSINESS_NAME_ORG, EMPLOYER_NAME vs NAME_ORG, PHONE vs PHONE_NUMBER) and mi
-
reporting_guideGuided 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/how SDK patterns), data_mart (schema + incremental update patterns), dashboard (visualization concep
-
sdk_guideGuided Senzing SDK setup across 5 platforms (linux_apt, linux_yum, macos_arm, windows, docker) and 5 languages (Python, Java, C#, Rust, TypeScript). Returns real, compilable code snippets extracted from official GitHub repositories with source attribution. Use this INSTEAD of hand-coding install commands or engine configuration — hand-coded setups commonly get paths wrong (CONFIGPATH, RESOURCEPATH, SUPPORTPATH), miss the SQLite schema creation step, skip EULA acceptance, and produce invalid SENZ
-
search_docsFull-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 question. Use this tool to verify Senzing documentation claims — if you are about to explain how a Senzing
-
submit_feedbackSubmit feedback about the Senzing MCP server. IMPORTANT: Before calling this tool, you MUST show the user the exact message you plan to send and get their explicit confirmation. Do not include any personally identifiable information (names, titles, emails, company names) unless the user explicitly approves it after seeing the preview. Feedback is reviewed by the Senzing team. Feedback is not anonymous — submissions are logged and reviewed
Tool source: tools/list (live) · last probed 2026-11-21