Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
Senzing is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Entity resolution — data mapping, SDK code generation, docs search, and error troubleshooting
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http senzing-mcp https://mcp.senzing.com/mcp
# 2 — ask your agent for something these tools do
# analyze_record, download_resource, explain_error_code and 10 more
Senzing costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SEAll 1 server
senzing1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http senzing-mcp https://mcp.senzing.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_paths | array/null | no | File paths to analyze (Senzing JSON or JSONL files). Commands will be generated for each path. |
| version | string | no | Senzing version (default: "current"). |
| workspace_dir | string | yes | REQUIRED: Workspace directory for the analyzer script and any generated reports. Must be a writable absolute or relative path that already exists in your environment. Do NOT assume /tmp exists — som |
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filename | string/null | no | Resource filename to retrieve (e.g. "sz_json_analyzer.py", "senzing_entity_specification.md"). Ignored when filenames is provided. |
| filenames | array/null | no | Multiple resource filenames to retrieve in a single call. Takes precedence over filename when provided. |
| inline | boolean/null | no | Returns resource content inline instead of fetch commands. NEVER the first call: run the resource's fetch command first, and set inline=true only if that command could not reach the server. This t |
| offset | integer/null | no | Character offset into the resource for inline=true pagination. Pass the next_offset from a previous truncated response. Default 0. |
| version | string | no | Senzing version (default: "current"). |
| workspace_dir | string/null | no | Directory the resources belong in — the mapping workflow's workspace_dir. Each resource's dest is <workspace_dir>/<filename>; omitted, dest is relative to your shell's current directory. Pass |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error_code | string | yes | — |
| version | string | no | — |
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: pass repo + list_files=true, (3) File retrieval: pass repo + file_path. Indexes source code
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | string/null | no | Return full content of a specific file in the repo (requires repo parameter) |
| language | string/null | no | Filter results by programming language (e.g. "python", "java", "csharp", "rust") |
| list_files | boolean/null | no | Return the file listing for a repo instead of searching (requires repo parameter) |
| max_lines | integer/null | no | Maximum lines to return for file content (default: unlimited). Useful for large files. |
| query | string/null | no | Search query (required for search mode, optional when using repo+file_path or repo+list_files) |
| repo | string/null | no | Filter to a specific indexed repo (e.g. "brianmacy/sz_mem-v4"). When combined with file_path, returns full file content. When combined with list_files, returns file listing. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | yes | Programming language: python, java, csharp (or c#, cs, dotnet), rust (or rs), typescript (or ts, node, nodejs, javascript, js) |
| version | string | no | Senzing version: "4.0", "current", or "3.x". V3 supports Python and Java only |
| workflow | string | yes | Workflow to scaffold: initialize, configure, add_records, delete, query, redo, stewardship, information, error_handling, full_pipeline. Aliases accepted (e.g. init, config, ingest, remove, search, red |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | Dataset name (e.g., "las-vegas", "london", "moscow"). Use "list" to discover available datasets and their sources. (Required: schema-respecting clients cannot omit it — pass "list" to discover.) |
| limit | integer/null | no | Number of records to PREVIEW inline in this response — at most 5; a larger value is capped. The inline records are a preview, NOT the dataset: for N records use the response's download_url (or its e |
| offset | no | Record offset. Use a number for explicit pagination, or "random" for a random starting position. Omit for random. | |
| source | string/null | no | Filter by data source/vendor within a dataset (e.g., "equifax", "ppp_loans"). Omit to see all sources. Use "list" to list available sources. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string/null | no | Optional filter: method name, class name, module name, or flag name. Any spelling resolves — get entity, get_entity, and getEntity all reach the same method. Examples are backticked, not double |
| language | string/null | no | Language binding: "python", "java", "csharp", "rust", or "typescript". Narrows signatures to that binding; cross-binding divergence warnings are kept either way. Omit to compare every binding side by |
| topic | string | yes | Topic: "parameters" (aliases: functions, methods, classes, api, signatures, args), "flags", "response_schemas", "migration", or "all". You do not need "parameters" just to see a signature: any topic |
| version | string | no | Senzing version (default: "current") |
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")
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string/null | no | Action to perform. ONLY these values are valid: start, advance, back, status, reset. |
| data | object | no | Step-specific data (for "advance" action). Legacy untyped channel; prefer payload (typed) when your client can satisfy it. |
| file_paths | array/null | no | Source file paths (required for "start" action). Also accepted inside data — see workspace_dir for why both placements are honoured. |
| output_path | no | Optional, "start" only: the output file the USER ASKED FOR, if any — the Senzing JSONL the mapper writes at step 4. Omit it to use the default <workspace_dir>/<name>_output.jsonl. Forms: a file path | |
| payload | object | no | Typed step payload for the "advance" action (H16). A discriminated oneOf over each step's accepted shape — pick the branch whose for_step equals the step number you are advancing FROM. When presen |
| state | object | no | Workflow state from previous response (required for all actions except "start"). CRITICAL: Pass the EXACT 'state' JSON object from the previous mapping_workflow response verbatim — do NOT reconstruct, |
| version | string | no | Senzing version (default: "current"). |
| workspace_dir | string/null | no | Writable output directory (required for "start" action). Historically this lived ONLY inside data while file_paths lived ONLY at the top level, so the two arguments of a single call sat in differe |
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/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string/null | no | Programming language. Omit to get the language decision tree. |
| scale | string/null | no | Scale tier. Omit to get the scale decision tree. |
| topic | string | yes | Topic: "export", "reports", "entity_views", "data_mart", "dashboard", "graph", "quality", "evaluation" |
| version | string | no | Senzing version (default "current") |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| data_sources | array/null | no | Data sources to register (for configure topic) |
| language | string/null | no | Programming language. Omit to get the language decision tree. |
| platform | string/null | no | Target platform. Choose linux_yum vs linux_apt from /etc/os-release on the TARGET host (ID / ID_LIKE), not from uname. Omit to get the platform decision tree — or, when the server runs locally (stdi |
| record_count | integer/null | no | Expected operation volume — number of records (load), queries (search), or pending redos (redo). When null or > 500, the primary code returned is the threaded/production pattern; when ≤ 500 it is the |
| topic | string | yes | Topic: "install", "configure", "load", "export", "redo", "initialize", "search", "stewardship", "delete", "information", "error_handling", or "full_pipeline" |
| version | string | no | Senzing version (default "current") |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string/null | no | Optional category boost: results from this category rank first, then are backfilled from all categories — it is NOT a hard filter, and an unknown value degrades to a broad search with a warning. Commo |
| max_results | integer/null | no | Maximum number of results to return (default 10, maximum 50). A larger value is clamped to 50 and the response carries a max_results_notice. |
| query | string | yes | — |
| version | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string/null | no | Category: bug, feature, question, general, or license_request |
| string/null | no | Work email address (required for license_request — personal email domains not accepted) | |
| firstname | string/null | no | First name of the requester (required for license_request) |
| how_heard | string/null | no | How the requester heard about Senzing (required for license_request) |
| lastname | string/null | no | Last name of the requester (optional for license_request) |
| message | string/null | no | Feedback message (required for bug/feature/question/general) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Senzing or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.37.29.
1.37.29
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Senzing can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.