# Tools changed: Senzing MCP (remote) > Source: > Published: 2026-11-11 00:00:00+00:00 # Senzing MCP (remote) **90**/100 Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. [Methodology](https://testedmcp.com/methodology/) - Install20/20 - Handshake30/30 - Maintenance25/25 - Docs15/15 - License0/10 Vendor-hosted The server source isn't public: Senzing hosts it at https://mcp.senzing.com/mcp, and github.com/Senzing/mcp holds only docs and the registry manifest, under an All rights reserved license (so license scores 0). Initialize and tools/list worked with no sign-in (13 tools, server sz-mcp-coworker 1.42.5), and 2 of 2 real read-only tool calls passed. The source still isn't public, which stays a caveat. On 2026-11-10 the 65 cap was lifted because the endpoint is on a product domain the vendor owns and real tool calls passed, so the score is 90. Tool-call test (2026-11-01, direct MCP stdio client, no LLM): **pass**. 2 of 2 read-only calls passed on the live endpoint: get_capabilities described the server and its 13 tools; explain_error_code explained SENZ0002. No credentials. Evidence: live endpoint probe, Nov 1, 2026. Senzing-hosted public endpoint, no sign-in. The server source isn't public: github.com/Senzing/mcp holds docs and server.json only, under an All rights reserved license. Listed as a hosted remote (Our review, Oct 31, 2026). Sources: [https://github.com/Senzing/mcp](https://github.com/Senzing/mcp) · [https://github.com/Senzing/mcp/commit/015af0b1c5](https://github.com/Senzing/mcp/commit/015af0b1c5) **Transport (tested 2026-11-01):** Streamable HTTP **Token cost (estimate):** approx. 9436 tokens, cl100k estimate (13 tools, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base. ## Permissions: 12 read, 1 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown Auth: none. Rate limit: unknown. Pricing unit: unknown. - `analyze_record` — read - `download_resource` — read - `explain_error_code` — read - `find_examples` — read - `generate_scaffold` — read - `get_capabilities` — read - `get_sample_data` — read - `get_sdk_reference` — read - `mapping_workflow` — read - `reporting_guide` — read - `sdk_guide` — read - `search_docs` — read - `submit_feedback` — write (state-changing) remote handshake listed tools without credentials; no recorded key or OAuth Score **90/100** · Tools **13** · Token cost **approx. 9,436 tokens** · [Compare](https://testedmcp.com/compare/?s=senzing-mcp-remote) · Last tested **2026-11-01** · Server version `1.42.5` · Remote endpoint `https://mcp.senzing.com/mcp` (streamable-http) Summary: Senzing MCP (remote) completed an MCP handshake without credentials and exposed 13 tools. ## Evidence summary - Handshake - pass - Tools listed - 13 - Context cost - approx. 9436 tokens, cl100k estimate (13 tools, measured 2026-11-11; an estimate) [ranking](https://testedmcp.com/best/lowest-context-cost-mcp-servers/) ·[add up your servers' context cost](https://testedmcp.com/guides/how-much-context-mcp-servers-cost/) - Login - No key needed for the tools we called - Tested - 2026-11-01 ## Test results | Test | Result | Points | Evidence | |---|---|---|---| | install | pass | 20 | Endpoint https://mcp.senzing.com/mcp reachable over streamable-http (HTTP 200) in 0.1s; no install step for remote servers. | | handshake | pass | 30 | MCP `initialize` (protocol 2025-06-18, server sz-mcp-coworker 1.42.5) +`tools/list` over streamable-http succeeded with no credentials; 13 tools listed in 0.1s. Tool calls may still need a key. | | maintenance | pass | 25 | Vendor-hosted rule: scored from dated commit in Senzing's docs repo 2026-10-31 (https://github.com/Senzing/mcp/commit/015af0b1c5), 1 day before test. Registry: com.senzing/mcp is in the official MCP registry with remote https://mcp.senzing.com/mcp (not used for scoring). | | docs | pass | 15 | official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://github.com/Senzing/mcp). | | license | fail | 0 | A public All rights reserved (proprietary, Senzing, Inc.) repo exists (https://github.com/Senzing/mcp), but it holds metadata only and its license does not cover the hosted service, so 0 (rule: no points without a cited license for the service). | ## Local-model readiness Token cost (estimate): **approx. 9436 tokens, cl100k estimate** for 13 tools · about 115% of an 8k context. This is an estimate from our testing (counted with cl100k_base). Small-model friendly (schema heuristic, not a model result): **unknown**. ## Not tested Small-model task runs: Not yet tested. ## What we tested and what we didn't ### Tested on 2026-11-01 - We connected to the vendor's hosted endpoint with no credentials and asked for its tool list: it listed 13 tools (Method details: MCP `initialize` then`tools/list` ) - Auth response: none. The endpoint answered without any login - Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15) - Maintenance: dated vendor source, dated commit in Senzing's docs repo 2026-10-31 (25/25) - License: a hosted service has no license to cite (0/10) - Token cost (estimate) ### Not tested - Security: **not audited** (hosted service; no code to review, no permission or data-flow analysis) - Behaviour after signing in, or with a real account - Source code, repository activity or an open-source license (none published for the hosted service) - Performance, rate limits or load - Real tasks (no functional task runs yet) Methodology: [how we test](https://testedmcp.com/methodology/) (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk. ## Known security issues Not checked (remote-only): hosted endpoint, version unknown. Monthly roundup: [MCP security issues, October 2026](https://testedmcp.com/security/2026-10/). ## Tool list changes ↻ Tools changed (non-breaking) 2026-11-11 **Tool list changed since last test (2026-11-01 → 2026-11-11): 1 tool description changed: find_examples; 3 input schemas changed: mapping_workflow, reporting_guide, sdk_guide.** Confirmed by a re-run with the same arguments. ## Show the diff - Changed description: `find_examples` - Changed schema: `mapping_workflow` - Changed schema: `reporting_guide` - Changed schema: `sdk_guide` ## Snapshot hash (fingerprint of the tool list) `3ef3e63d7b76`: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed. ## Raw test record (JSON) ``` { "name": "senzing-remote", "version": null, "registry": "remote", "status": "working", "tested": "2026-11-01", "tools_count": 13, "deprecated": false, "archived": null, "tests": { "install": [ "pass", 20, "Endpoint https://mcp.senzing.com/mcp reachable over streamable-http (HTTP 200) in 0.1s; no install step for remote servers." ], "handshake": [ "pass", 30, "MCP `initialize` (protocol 2025-06-18, server sz-mcp-coworker 1.42.5) + `tools/list` over streamable-http succeeded with no credentials; 13 tools listed in 0.1s. Tool calls may still need a key." ], "maintenance": [ "pass", 25, "Vendor-hosted rule: scored from dated commit in Senzing's docs repo 2026-10-31 (https://github.com/Senzing/mcp/commit/015af0b1c5), 1 day before test. Registry: com.senzing/mcp is in the official MCP registry with remote https://mcp.senzing.com/mcp (not used for scoring)." ], "docs": [ "pass", 15, "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://github.com/Senzing/mcp)." ], "license": [ "fail", 0, "A public All rights reserved (proprietary, Senzing, Inc.) repo exists (https://github.com/Senzing/mcp), but it holds metadata only and its license does not cover the hosted service, so 0 (rule: no points without a cited license for the service)." ] } } ``` ## Install `https://mcp.senzing.com/mcp` ## Tools listed `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` Tool history: captured Nov 11, 2026. [All tool history](https://testedmcp.com/changes/). ## Quick config ``` { "mcpServers": { "senzing-mcp-remote": { "type": "http", "url": "https://mcp.senzing.com/mcp" } } } ``` [Add to config](https://testedmcp.com/free-tools/mcp-config-generator/?s=senzing-mcp-remote) Opens the config generator with this server selected. ## Setup 1. **Install.** No install step: it is a remote server at https://mcp.senzing.com/mcp. 2. **Configure.** Add the mcpServers entry below to your MCP client config. 3. **Verify.** Restart the client and check that tools/list returns tools (13 in our test). ``` { "mcpServers": { "senzing-mcp-remote": { "type": "http", "url": "https://mcp.senzing.com/mcp" } } } ``` ## Test history - 2026-11-11: Permission card updated - 2026-11-11: Tools changed (non-breaking) - 2026-11-01: New Related: [Best data and analytics MCP servers](https://testedmcp.com/best/data-mcp-servers/) ## FAQ ### Is Senzing MCP deprecated? No. senzing-remote was not deprecated or archived when we last tested it on 2026-11-01. ### What replaces Senzing MCP? Nothing; Senzing MCP (remote) is not deprecated as of 2026-11-01. ### Does Senzing MCP need an API key? No. It completed an MCP handshake with no credentials and listed 13 tools. ## Embed the badge Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.