Skip to content
Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
66
A2A A2A 1.0 v1.39.4

Senzing Entity Resolution

mcp.senzing.com · Senzing, Inc.

Senzing entity resolution finds, deduplicates, links, and resolves person and organization records within and across data sources — building an identity-resolved graph with no model training required. Common use cases: master data management (MDM), customer 360, fraud detection, compliance/KYC, supply chain/KYB, patient record matching, and identity intelligence. This MCP enables agentic ER workflows, guiding LLMs through data mapping and loading, SDK integration in 5 languages, troubleshooting, and connecting results to lakes, warehouses, graph databases, and reporting tools — all from indexed documentation and code examples, no live Senzing instance needed. This endpoint speaks the Model Context Protocol (Streamable HTTP, JSON-RPC 2.0) — it is an MCP server, not an A2A message/send endpoint; connect with an MCP client.

Build a free agent shortlist. Save this listing to revisit it from your account. Sign in to save
🛡
Own this agent?
Verify the domain mcp.senzing.com via a single DNS TXT record to add the verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Verify ownership

Compare public evidence

🔔 Watch this agent. Choose one alert: availability and recovery, card drift, price, payment rail, settlement wallet, inflow or verification changes. Add more alert types from your account. Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro. Sign in to watch
Trust score
66/100
grade C · 9 criteria
Uptime
100.0%
56 direct probes · 30d
~45 ms response
Observed inflow · 30d
—
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
changed
10 snapshots tracked
Owner
unverified
claim this listing →

Dispute or improve this rating

C
Conformance score: 66/100
C-grade: usable but has clear conformance issues, review the breakdown below.
click to expand breakdown click to collapse breakdown
pass Valid AgentCard 10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
partial Live JSON-RPC 10/25
Card declares only gRPC / HTTP+JSON interfaces; the live probe covers JSON-RPC, so the endpoint was not exercised. Not a defect in the card.
How to earn +15 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (current v1 card shape).
info JWS signature 0/10
Card is unsigned (most published agents are).
pass Uptime track record 15/15
56/56 probes succeeded (100% uptime).
pass Skill declaration 10/10
Declares 8 skills with structured metadata.
partial Verified Identity 5/10
Provider declared: Senzing, Inc. (https://senzing.com). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs
pass Freshness + modern flags 4/5
seen in upstream source within 0d
partial Security declaration 2/5
Declares securityRequirements: [] — deliberately public, no credentials required.
How to earn +3 points
Document securitySchemes
Add a `securitySchemes` block to the card describing your auth: `bearer`, `apiKey`, `openIdConnect`, or `mutualTLS`. Routers refuse to call agents that declare no auth model.
Docs
Card drift detected. This agent's agent-card.json changed within the last 7 days. We track these so downstream callers can react.

Activity (audit trail)

last 24h · 0 invocations Public aggregate · no PII recorded

Nothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.

Card history

10 snapshots drifted 9× Every change to agent-card.json
Agent card snapshots
Captured Hash Snapshot
2026-10-24 15:13:16 current df03502b91de… view →
2026-10-16 11:34:06 7cec1acb45a4… view →
2026-10-15 17:47:47 019c139def84… view →
2026-10-15 01:18:10 ff57f183b866… view →
2026-10-14 13:46:49 c9374b0b7c32… view →
2026-10-13 13:15:56 572bfb0bab25… view →
2026-10-11 21:30:38 88e8980d6b1d… view →
2026-10-10 01:31:29 26bec5c088f2… view →
2026-10-09 13:54:05 8d53d538d653… view →
2026-10-08 15:22:29 f8dbf5fa72d6… view →
Showing latest 10. The full snapshot history is on Pro (and free for the verified owner) via GET /api/agents/mcp.senzing.com/snapshots.
Uptime
100.0%
56 direct probes · 30d
Response
75ms
last direct probe
Skills
8
declared
Streaming
—
SSE-capable

Endpoints

Agent cardhttps://mcp.senzing.com/.well-known/agent-card.json
Providerhttps://senzing.com
Docshttps://mcp.senzing.com/
About this provider off-card enrichment
SSL certificate
Let's Encrypt
expires 2026-11-18
Discovered via
smithery recrawl_hot mcp_registry recrawl_warm

Skills · 8 declared by this agent

These skills are declared by the agent. A taxonomy link appears only when we can classify a skill confidently.

Data Mapping

Prepare source data for entity resolution so Senzing can match and link records. Interactive 8-step workflow: profile source fields, plan entity structure, map …

No taxonomy category yet
data-mappingentity-resolutionetljsonvalidation
SDK Integration

Build entity resolution into your application. Scaffold working code, set up the SDK, and get API reference across Python, Java, and C# (official SDKs) plus Rus…

No taxonomy category yet
sdkcode-generationpythonjavacsharp
Documentation & Examples

Find answers to Senzing entity resolution questions. Full-text search across indexed documentation and 53 GitHub repositories with real code examples for config…

No taxonomy category yet
documentationsearchknowledge-basegithubexamples
Error Troubleshooting

Diagnose and resolve Senzing errors. Look up 461 indexed error codes with root causes, resolution steps, and links to related documentation.

canonical Error Diagnosis and Debugging match 87%
errorstroubleshootingdebuggingdiagnosticssupport
Sample Data

Explore real-world entity resolution data to evaluate matching quality. CORD dataset records from Las Vegas, London, and Moscow, plus the Senzing demo truth set…

No taxonomy category yet
sample-datacordtestingentity-resolutiondatasets
Reporting & Analytics

Extract insights from entity resolution results. SDK patterns for data export, SQL analytics queries, data mart schemas, dashboard design, and resolution qualit…

No taxonomy category yet
reportingvisualizationanalyticsdashboardsql
Platform Engineering & Deployment

Design and operate Senzing in production. Cloud reference architectures (AWS, Azure, GCP), backing-database selection and sizing, replication and read replicas,…

No taxonomy category yet
platform-engineeringdeploymentcloudawsazure
Evaluation & Demos

Evaluate Senzing fast with no infrastructure. Build a quick local demo from your own data, run entity resolution on real sample data, and evaluate match quality…

No taxonomy category yet
evaluationdemopoctrialquickstart

Health · last 30 probes

When HTTP Live JSON-RPC Latency
2026-10-25 05:19:27 200 — 75ms
2026-10-24 15:13:16 200 — 32ms
2026-10-24 02:48:49 err — —
2026-10-23 13:46:19 200 — 32ms
2026-10-23 01:59:10 200 — 33ms
2026-10-22 12:30:12 200 — 28ms
2026-10-21 23:17:51 200 — 37ms
2026-10-21 09:57:42 200 — 32ms
2026-10-20 20:39:31 200 — 35ms
2026-10-20 03:02:19 200 — 45ms

Who's calling this agent 30d

1 interactions captured (impressions + lookups + A2A calls)

By AI host (caller_kind) · top 3
curl 1 (100%)
Caller geography · top 3
NL 1
Via which API surface · top 3
rest 1

Public view: top 3 per dimension. Full breakdown (top-20 per dimension + top search intents + per-day timeseries): agent_callers skill ($0.05/call, $0 on Enterprise). Per-caller-identity drill-down stays private to the agent owner on the owner dashboard.

Cheaper or better alternatives per-skill

↑ 1 higher quality

For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.

Similar agents embedding-nearest

entity-resolve.x402supply.com
Fuzzy-dedupe a list of records into clusters of likely-duplicate entities. Blocks by normalized token prefix, scores with Jaro-Winkler + tok
entity-resolve.x402supply.com · q 65%
deadends.dev
Structured error knowledge database for AI coding agents. 2725 error patterns across 54 domains (android, api, aws, banking, cicd, cloud, cm
deadends.dev · q 80%
x402-entity-resolver-production.up.railway.app
Resolves entity data through a paid API endpoint for Base USDC.
x402-entity-resolver-production.up.railway.app · q 65%
Sentry Forge — Consumer-Debt Dispute Pack (RAEN x402) live
Turn a third-party debt-collection notice into an 8-file review-ready validation and complaint pack. Get markdown docs (collector letter, CF
Royal Agentic Enterprises · q 100%
Scholar Sidekick live
Citation resolver, formatter, exporter, and verifier for scholarly identifiers (DOI, PMID, PMCID, ISBN, ISSN, arXiv, ADS, WHO IRIS). Connect
Scholar Sidekick · q 100%
KR-ECO-10060 — South Korea — Canonical
Sovereign jurisdictional resolver for South Korea under Standard-10060. Member of SM-ECO-10060.
GreenCore Solutions Corp. · q 78%

Embed your Agenstry badge

Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.

Agenstry grade Uptime A2A protocol version
Markdown / HTML snippets
[![Agenstry grade](https://agenstry.com/badge/mcp.senzing.com.svg)](https://agenstry.com/agents/mcp.senzing.com)
[![Verified Business](https://agenstry.com/badge/mcp.senzing.com/identity.svg)](https://agenstry.com/agents/mcp.senzing.com)
[![Uptime](https://agenstry.com/badge/mcp.senzing.com/uptime.svg)](https://agenstry.com/agents/mcp.senzing.com)
[![A2A version](https://agenstry.com/badge/mcp.senzing.com/protocol.svg)](https://agenstry.com/agents/mcp.senzing.com)

Audit-grade evidence bundle

JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against our JWKS. See the methodology.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON
{
  "name": "Senzing Entity Resolution",
  "description": "Senzing entity resolution finds, deduplicates, links, and resolves person and organization records within and across data sources \u2014 building an identity-resolved graph with no model training required. Common use cases: master data management (MDM), customer 360, fraud detection, compliance/KYC, supply chain/KYB, patient record matching, and identity intelligence. This MCP enables agentic ER workflows, guiding LLMs through data mapping and loading, SDK integration in 5 languages, troubleshooting, and connecting results to lakes, warehouses, graph databases, and reporting tools \u2014 all from indexed documentation and code examples, no live Senzing instance needed. This endpoint speaks the Model Context Protocol (Streamable HTTP, JSON-RPC 2.0) \u2014 it is an MCP server, not an A2A message/send endpoint; connect with an MCP client.",
  "version": "1.39.4",
  "supportedInterfaces": [
    {
      "url": "https://mcp.senzing.com/mcp",
      "protocolBinding": "MCP",
      "protocolVersion": "1.0"
    }
  ],
  "provider": {
    "organization": "Senzing, Inc.",
    "url": "https://senzing.com"
  },
  "documentationUrl": "https://mcp.senzing.com/",
  "iconUrl": "https://mcp.senzing.com/favicon.ico",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "securitySchemes": {},
  "securityRequirements": [],
  "defaultInputModes": [
    "text/plain",
    "application/json"
  ],
  "defaultOutputModes": [
    "text/plain",
    "application/json"
  ],
  "skills": [
    {
      "id": "data-mapping",
      "name": "Data Mapping",
      "description": "Prepare source data for entity resolution so Senzing can match and link records. Interactive 8-step workflow: profile source fields, plan entity structure, map to Senzing attributes, generate validated JSON output, and optionally test with the SDK.",
      "tags": [
        "data-mapping",
        "entity-resolution",
        "etl",
        "json",
        "validation",
        "deduplication",
        "record-linkage"
      ],
      "examples": [
        "Map my customer CSV to Senzing format",
        "Help me map these source fields to entity resolution attributes",
        "Validate my Senzing JSON mapping"
      ]
    },
    {
      "id": "sdk-development",
      "name": "SDK Integration",
      "description": "Build entity resolution into your application. Scaffold working code, set up the SDK, and get API reference across Python, Java, and C# (official SDKs) plus Rust and TypeScript (community wrappers), on 5 platforms. Includes V3-to-V4 migration guidance for existing Senzing integrations.",
      "tags": [
        "sdk",
        "code-generation",
        "python",
        "java",
        "csharp",
        "rust",
        "typescript",
        "integration",
        "migration"
      ],
      "examples": [
        "Generate Python code to initialize and load data with Senzing",
        "Set up the Senzing Java SDK on Docker",
        "How do I migrate from Senzing V3 to V4?"
      ]
    },
    {
      "id": "documentation-search",
      "name": "Documentation & Examples",
      "description": "Find answers to Senzing entity resolution questions. Full-text search across indexed documentation and 53 GitHub repositories with real code examples for configuration, deployment, and API usage.",
      "tags": [
        "documentation",
        "search",
        "knowledge-base",
        "github",
        "examples",
        "configuration",
        "deployment"
      ],
      "examples": [
        "How do I configure Senzing for PostgreSQL?",
        "Find Python examples for entity search",
        "What are entity resolution principles?"
      ]
    },
    {
      "id": "error-troubleshooting",
      "name": "Error Troubleshooting",
      "description": "Diagnose and resolve Senzing errors. Look up 461 indexed error codes with root causes, resolution steps, and links to related documentation.",
      "tags": [
        "errors",
        "troubleshooting",
        "debugging",
        "diagnostics",
        "support"
      ],
      "examples": [
        "What does Senzing error 2089 mean?",
        "How do I fix SENZ-0033?"
      ]
    },
    {
      "id": "sample-data",
      "name": "Sample Data",
      "description": "Explore real-world entity resolution data to evaluate matching quality. CORD dataset records from Las Vegas, London, and Moscow, plus the Senzing demo truth set, with discovery and pagination.",
      "tags": [
        "sample-data",
        "cord",
        "testing",
        "entity-resolution",
        "datasets",
        "evaluation",
        "poc"
      ],
      "examples": [
        "Show me sample records from the Las Vegas dataset",
        "What sample data is available for testing?"
      ]
    },
    {
      "id": "reporting",
      "name": "Reporting & Analytics",
      "description": "Extract insights from entity resolution results. SDK patterns for data export, SQL analytics queries, data mart schemas, dashboard design, and resolution quality evaluation across 5 languages.",
      "tags": [
        "reporting",
        "visualization",
        "analytics",
        "dashboard",
        "sql",
        "export",
        "data-quality"
      ],
      "examples": [
        "How do I export entity resolution results?",
        "Show me SQL queries for Senzing analytics",
        "Help me build a reporting dashboard"
      ]
    },
    {
      "id": "platform-engineering",
      "name": "Platform Engineering & Deployment",
      "description": "Design and operate Senzing in production. Cloud reference architectures (AWS, Azure, GCP), backing-database selection and sizing, replication and read replicas, high availability and failover, and infrastructure-as-code.",
      "tags": [
        "platform-engineering",
        "deployment",
        "cloud",
        "aws",
        "azure",
        "gcp",
        "kubernetes",
        "database",
        "replication",
        "high-availability",
        "terraform"
      ],
      "examples": [
        "Give me an AWS reference architecture for Senzing at 50M records",
        "Which database should I use and how do I size it?",
        "Design a highly-available deployment with read replicas"
      ]
    },
    {
      "id": "evaluation",
      "name": "Evaluation & Demos",
      "description": "Evaluate Senzing fast with no infrastructure. Build a quick local demo from your own data, run entity resolution on real sample data, and evaluate match quality on the free tier.",
      "tags": [
        "evaluation",
        "demo",
        "poc",
        "trial",
        "quickstart",
        "sample-data",
        "entity-resolution"
      ],
      "examples": [
        "Here's my customer CSV \u2014 build me a working demo I can show",
        "Load this sample data and show me the duplicates Senzing finds",
        "Help me evaluate resolution quality"
      ]
    }
  ]
}