Senzing MCP server
com.senzing/mcpsenzing.comstreamable-httpv1.46.3Scanned
Entity resolution — data mapping, SDK code generation, docs search, and error troubleshooting
13 tools: 5 change things and 8 only read.
- Reads private data · 4
- Reads text others write · 1
- Can send data out · 0
- 5 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Senzing MCP server can do
The Senzing MCP server is published by senzing.com, a domain the MCP Registry verified. It has 13 tools. It can create or change data (5 tools: generate_scaffold, mapping_workflow, reporting_guide, sdk_guide and 1 more), but cannot delete data. 8 tools only read.
4 tools read private data (analyze_record, download_resource, find_examples and 1 more); 1 tool brings in text other people can write (submit_feedback).
The fixed checks matched 5 findings (annotation-conflict and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 9 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.46.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 5Claude Code: ask
generate_scaffoldGenerate SDK scaffold code for common workflows.1 finding
Why it is in this group
- The name "generate_scaffold" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_scaffold" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_scaffold" says "generate": a word for a change.
Description, as the server wrote it 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. Languages: python, java, csharp (official V4 SDKs); rust, typescript (community-maintained wrappers, not official). Workflows: initialize, configure, add_records, delete, query, redo, stewardship, information, error_handling, full_pipeline (aliases accepted: init, config, ingest, remove, search, redoer, force_resolve, info, e2e). V3 supports Python only. Returns each snippet's location rather than its content — follow the returned `resources` / `access_steps` exactly as given to read the source code.
Annotations the server declares
- title: Generate SDK Scaffold
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mapping_workflowMap source data to Senzing JSON through a guided 8-step workflow.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 3,158 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...NAME vs NAME_ORG, PHONE vs PHONE_NUMBER) and miss required fields like RECORD_ID."
Description, as the server wrote it Map source data to Senzing JSON through a guided 8-step workflow. Use this INSTEAD of hand-coding Senzing JSON. Optional `environment` — one of snowflake, aws_lambda, azure_functions, kafka, spark, databricks (aliases such as spcs, snowpark, lambda, azure_function, kafka_connect, apache_kafka, apache_spark, pyspark, lakebase, unity_catalog, sz_databricks, databricks_sql are accepted) — names where this deployment runs; the response then opens with `environment_note`, the rules for that environment and the search_docs query to run before writing code or SQL. For mapping_workflow the note is on the start response only; dotted DB.SCHEMA.TABLE source labels (bare or with a data-file extension) infer environment=snowflake. 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") — a writable directory where scripts, reference docs, mapper code, and outputs are saved. Do NOT assume /tmp exists (some environments like Kiro do not provide it). The call needs both arguments present; it does NOT need the file to exist. OPTIONAL on start: `output_path` — the output file the USER ASKED FOR, if any (a .jsonl path; a directory ending in / for one <schema_name>.jsonl per schema; or a per-schema map {"<schema_name>": "<path>.jsonl"}). Omit it for the default <workspace_dir>/<name>_output.jsonl. Start arguments are accepted at the top level or inside `payload`. NO READABLE FILE, NO SHELL — START ANYWAY. If the user only DESCRIBED their columns, or you have no shell to run the profiler, step 1 accepts a `profile_summary` you write yourself: field_count from their column list, record_count as they stated it or 0 (zero means 'not measured' and is expected — it is not fabrication). An unreadable source file is NOT a reason to hand-code a mapping instead. Actions: start, advance, back, status, reset. 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. STATE: Every response returns a 'state' JSON object. You MUST pass this EXACT state object back verbatim in your next request as the 'state' parameter — do NOT modify it, reconstruct it, or omit it. The state is opaque and managed by the server. If you have lost the state, call with action='start' instead. Common errors: (1) omitting state on advance — always include it, (2) reconstructing state from memory — always echo the exact JSON from the previous response, (3) omitting payload on advance — each step requires specific payload fields documented in the instructions (`data` is a legacy alias of `payload`), (4) omitting the file_paths or workspace_dir ARGUMENTS on start — the server needs the names, not a readable file. Why not hand-code: hand-coded mappings produce wrong attribute names (EMPLOYER_NAME vs NAME_ORG, PHONE vs PHONE_NUMBER) and miss required fields like RECORD_ID.
Annotations the server declares
- title: Data Mapping Workflow
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
reporting_guideGuided reporting and visualization for Senzing entity resolution results.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Guided reporting and visualization for Senzing entity resolution results. Optional `environment` — one of snowflake, aws_lambda, azure_functions, kafka, spark, databricks (aliases such as spcs, snowpark, lambda, azure_function, kafka_connect, apache_kafka, apache_spark, pyspark, lakebase, unity_catalog, sz_databricks, databricks_sql are accepted) — names where this deployment runs; the response then opens with `environment_note`, the rules for that environment and the search_docs query to run before writing code or SQL. 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 concepts + data sources), graph (network export patterns), quality (precision/recall/F1, split/merge detection, review queues, sampling strategies), evaluation (4-point ER evaluation framework with evidence requirements, export iteration stats methodology, MATCH_LEVEL_CODE reference). Returns decision trees when language/scale not specified.
Annotations the server declares
- title: ER Reporting Guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
sdk_guideInstall 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 — H…2 findings
Why it is in this group
- The description's first verb is "install": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 2,073 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...wnload instruction stops working, call this tool again to obtain the current one."
- Warn
The server marks "sdk_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "install": a word for a change.
Description, as the server wrote it 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). Optional `environment` — one of snowflake, aws_lambda, azure_functions, kafka, spark, databricks (aliases such as spcs, snowpark, lambda, azure_function, kafka_connect, apache_kafka, apache_spark, pyspark, lakebase, unity_catalog, sz_databricks, databricks_sql are accepted) — names where this deployment runs; the response then opens with `environment_note`, the rules for that environment and the search_docs query to run before writing code or SQL. 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 install and this server runs on the install host itself, it detects the platform from that host's os-release. Languages: 5 (Python, Java, C#, Rust, TypeScript). Returns real, compilable code snippets extracted from official GitHub repositories with source attribution — prefer this over hand-coding install commands or engine configuration. When this server carries the SDK packages for the chosen platform (.deb for linux_apt, .rpm for linux_yum, the macOS packages for macos_arm, and the .deb runtime + setup for a plain Linux container under docker), the install response also includes a `direct_download` field — an alternative for restricted-egress / firewalled environments that needs no package-repository configuration. Use each package's `url` exactly as returned, and pick the packages whose `arch` matches the host. Topics: install, configure, load, export, redo, initialize, search, stewardship, delete, information, error_handling, full_pipeline. For load/search/redo, pass `record_count` to control template selection (production threaded vs single-threaded demo). Export redirects to reporting_guide. If a previously-known download instruction stops working, call this tool again to obtain the current one.
Annotations the server declares
- title: SDK Setup Guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submit_feedbackRequest a free Senzing evaluation license or submit feedback.Reads text others writeNo findings
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 bug/feature/question/general and provide message. Show the user the exact message and get confirmation before sending.
Annotations the server declares
- title: Submit Feedback
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 8Show 8 read-only tools
analyze_recordGet the Senzing JSON analyzer script to validate mapped data files client-side.Reads private dataNo findings
Why it is in this group
- The name "analyze_record" says "analyze": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "file": it reads files.
- private-dataThe input names a file (input.file_paths), and the tool reads: it reads files.
Description, as the server wrote it 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 to the server. Typical workspace_dir values: Linux `/tmp` or `~/sz-workspace`; macOS `~/sz-workspace`; sandboxed envs: explicit path under home (do NOT assume /tmp exists).
Annotations the server declares
- title: Analyze Senzing JSON
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
download_resourceReturns resource URLs/content in this response; it does NOT write any files.Reads private dataNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it 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_dir` (the mapping workflow's) so `dest` matches the workflow's paths; calling with neither filename returns the list of available resources (it does not fail). Available: sz_json_analyzer.py, sz_schema_generator.py, sz_verbatim_check.py, sz_routing_report.py, senzing_entity_specification.md, senzing_mapping_examples.md, identifier_crosswalk.json mapping_workflow and analyze_record already return each resource's `fetch` command — you do not need this tool to run them. If a previously-known fetch instruction stops working, call this tool again to obtain the current one.
Annotations the server declares
- title: Download Resource
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_error_codeExplain a Senzing error code with causes and resolution steps.No findings
Why it is in this group
- The name "explain_error_code" says "explain": a word for reading.
Description, as the server wrote it 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
Annotations the server declares
- title: Explain Error Code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_examplesFind working SOURCE CODE examples from 53 indexed Senzing GitHub repositories.Reads private dataNo findings
Why it is in this group
- The name "find_examples" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "repository": it reads repositories.
- private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
Description, as the server wrote it 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 (.py, .java, .cs, .rs, .ts, .js) and READMEs — NOT build/data files. For sample data, use get_sample_data. Covers Python, Java, C# (official SDKs) plus Rust and TypeScript/Node.js (community-maintained wrappers, not official) SDK patterns: initialization, ingestion, search, redo, configuration, message queues, REST APIs. Use max_lines to limit large files. File retrieval returns the file's location instead of its content: follow the returned `resources` / `access_steps` exactly as given.
Annotations the server declares
- title: Find Code Examples
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_capabilitiesGet server version, capabilities overview, available tools, suggested workflows, and getting started guidance.No findings
Why it is in this group
- The name "get_capabilities" says "get": a word for reading.
Description, as the server wrote it 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, deployment, troubleshooting, database, configuration, data mapping, etc.) — use it to triage which Senzing MCP tool to call before going to external sources
Annotations the server declares
- title: Get Server Capabilities
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_sample_dataGet sample data for entity resolution.1 finding
Why it is in this group
- The name "get_sample_data" says "get": a word for reading.
Findings
- Info
The description is 2,011 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...wnload instruction stops working, call this tool again to obtain the current one."
Description, as the server wrote it 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 explicit pagination or the string "random" (the default when omitted) for a random starting position. IMPORTANT: The three CORD datasets ('las-vegas', 'london', 'moscow') are REAL data (not synthetic) — historical snapshots for evaluation only, not operational use. Always inform the user of this. This does NOT apply to 'truthset', which is Senzing's own synthetic demo truth set (github.com/Senzing/truth-sets) — do not describe those records as real people's data. Each response's citation carries the provenance for the dataset actually returned; follow it rather than this summary. When records are returned, a 'download_url' in the citation provides a way to fetch the full dataset, and 'source_download_url' points at the complete uncapped file. Always present the fetch instruction to the user exactly as given. Downloading the dataset TO DISK is expected and encouraged whenever the user wants the data — run the returned download instruction in a shell (a URL to fetch with curl/wget, or a local command) to write it to a file, and work from that file. What you must NOT do is pull the dataset INTO THE CONVERSATION: never echo, cat, paste or summarise raw records back into context, because these files run to hundreds of thousands of records. The inline records above are a small preview of the data shape, not the delivery mechanism. (An earlier wording of this line said only 'Do NOT download it yourself', which was read as a blanket ban on fetching and left users downloading files by hand.) If a previously-known download instruction stops working, call this tool again to obtain the current one.
Annotations the server declares
- title: Get Sample Data
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_sdk_referenceGet authoritative Senzing SDK reference data: method signatures and argument types per language binding, flags, response schemas, and V3→V4 migration.No findings
Why it is in this group
- The name "get_sdk_reference" says "get": a word for reading.
Description, as the server wrote it 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 for — so looking up a method's flags also tells you what it takes. Topics: 'parameters' (aliases: functions, methods, classes, api, signatures, args) returns argument types per binding — the same method differs by binding in BOTH name and argument types: Python find_network_by_entity_id takes List[int], Java findNetwork takes SzEntityIds, C# FindNetwork takes ISet<long>, Rust takes &[EntityId], TypeScript findNetwork takes Array<number> and renames buildOutDegrees to buildOutDegree; 'flags' (all V4 engine flags and the methods they apply to; with a method filter: one line per applicable flag — NAME (default) — meaning, composites as NAME = A|B|C — under group headers, most specific to the method first, under 5k chars); 'flag_details' (the full definitions and response paths for a method filter); 'response_schemas' (JSON response structure per method); 'migration' (V3→V4 breaking changes, renames, flag changes); 'all'. 'filter' accepts any spelling — 'get entity', 'get_entity', and 'getEntity' all resolve. Pass 'language' (python/java/csharp/rust/typescript) to narrow to your binding; cross-binding divergence warnings are still included so you never translate a call between bindings by mistake
Annotations the server declares
- title: Get SDK Reference
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_docsFull-text BM25 search across all indexed Senzing documentation (~13.5k chunks).Reads private dataNo findings
Why it is in this group
- The name "search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "search_docs" says "search" and "doc": it reads documents.
Description, as the server wrote it Full-text BM25 search across all indexed Senzing documentation (~13.5k chunks). Returns ranked results with excerpts. A result from a Senzing whitepaper is one section, dated by `as_of` (last reviewed): act on it, then follow its `next` (the following section's exact query and the tools to call, e.g. sdk_guide with environment). 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 feature works, search here first rather than relying on training data.
Annotations the server declares
- title: Search Documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.senzing.com/mcp: tools/list returned 13 tools to an anonymous client, including generate_scaffold (write), mapping_workflow (write), reporting_guide (write), sdk_guide (write), submit_feedback (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "generate_scaffold" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_scaffold" says "generate": a word for a change.
- Warnsdk_guide
The server marks "sdk_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "install": a word for a change.
- Infoget_sample_data
The description is 2,011 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...wnload instruction stops working, call this tool again to obtain the current one."
- Infomapping_workflow
The description is 3,158 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...NAME vs NAME_ORG, PHONE vs PHONE_NUMBER) and miss required fields like RECORD_ID."
- Infosdk_guide
The description is 2,073 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...wnload instruction stops working, call this tool again to obtain the current one."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:submit_feedbackChanges thingsannotations
Tools4 changed.~4 changedView diff
- Changed:find_examplesOnly readsdescription
- Changed:mapping_workflowChanges thingsdescriptioninputSchema
- Changed:reporting_guideChanges thingsdescriptioninputSchema
- Changed:sdk_guideChanges thingsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:mapping_workflowChanges thingsinputSchema
Tools1 changed.~1 changedView diff
- Changed:find_examplesOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:download_resourceOnly readsdescriptioninputSchema
- Changed:search_docsOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:download_resourceOnly readsdescriptioninputSchema
- Changed:search_docsOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:get_sdk_referenceOnly readsinputSchema
Tools4 changed.~4 changedView diff
- Changed:get_sdk_referenceOnly readsdescription
- Changed:mapping_workflowChanges thingsdescriptioninputSchema
- Changed:reporting_guideChanges thingsdescriptioninputSchema
- Changed:sdk_guideChanges thingsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:find_examplesOnly readsdescription
Install
Pinned to version 1.46.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http senzing https://mcp.senzing.com/mcpclaude mcp add --transport http senzing https://mcp.senzing.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__senzing__analyze_record",
"mcp__senzing__download_resource",
"mcp__senzing__explain_error_code",
"mcp__senzing__find_examples",
"mcp__senzing__get_capabilities",
"mcp__senzing__get_sample_data",
"mcp__senzing__get_sdk_reference",
"mcp__senzing__search_docs"
],
"ask": [
"mcp__senzing__generate_scaffold",
"mcp__senzing__mapping_workflow",
"mcp__senzing__reporting_guide",
"mcp__senzing__sdk_guide",
"mcp__senzing__submit_feedback"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as senzing. Review it before you use it.
Capability tags behind 5 rules
- mcp__senzing__analyze_record private-data
- mcp__senzing__download_resource private-data
- mcp__senzing__find_examples private-data
- mcp__senzing__search_docs private-data
- mcp__senzing__submit_feedback untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.senzing/mcp/verify?hash=17c0d7484bf981ca9a90c54c4bd8d2fa4dfcccadb24ddc52858c607ac19fac97" | jq -e '.changed == false'Pinned hash 17c0d7484bf9, from Nov 20, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.senzing/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.senzing/mcp)Source: MCP Registry · repository. Synced Nov 20, 2026, 21:17 UTC.
Senzing MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Senzing MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 5 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Senzing MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Senzing MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Senzing MCP server have?
- 13 tools: 5 write, 8 read. generate_scaffold, mapping_workflow, reporting_guide, sdk_guide, submit_feedback, analyze_record, download_resource, explain_error_code and 5 more.
Does the Senzing MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Senzing MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Senzing MCP server changed its tools?
- Yes, 9 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.