IBM puts Dun & Bradstreet’s commercial graph behind an MCP server

IBM has added the Dun & Bradstreet Commercial Graph to the watsonx Orchestrate Agent Catalog through a Model Context Protocol server, giving enterprise agents a packaged route to verified company data. IBM’s Aug. 12 announcement says the connector is live now.

The immediate use cases are not generic chatbot demos. IBM points to finance, credit, procurement, compliance, sales and marketing workflows, with the D-U-N-S Number acting as a common company identifier across systems of record. The MCP server can retrieve and analyze D&B commercial data while operating inside D&B’s existing quality controls, permissions and audit trails, according to the announcement.

Why this matters for data-agent teams

For practitioners building natural-language interfaces to enterprise data, generating a plausible query is only one part of the system. The agent also needs authoritative entity context, current data and a controlled way to reach it. IBM’s catalog model packages that access as a reusable capability rather than asking each implementation team to build and maintain another proprietary connector.

That separation is important. A text-to-SQL layer can answer questions about tables already inside a warehouse, while a commercial-graph service supplies verified external context such as company identity, financial-health indicators and relationship mappings. An orchestration layer can combine the two without pretending they are the same data source or applying the same access policy to both.

IBM says watsonx Orchestrate provides centralized control for building, monitoring and scaling agents across cloud and on-premises systems. The company also says the D&B server can support near-real-time company research, supplier-risk checks, credit assessment and cross-system workflows.

What to verify before adoption

The announcement makes broad deployment claims, including that teams can reduce agent-to-data connection work from months to days, but it does not publish a benchmark or a detailed pricing model. Buyers should therefore treat that statement as vendor guidance, not a guaranteed implementation timeline.

A practical evaluation should test four things: which D&B fields the server exposes; how watsonx and D&B permissions combine; what audit records are available for each agent call; and whether the returned company identity can be joined reliably to internal customer, supplier and account records. Teams should also measure freshness and failure behavior for the exact jurisdictions and business entities they use.

The larger signal is architectural: enterprise agents are beginning to consume governed data products through standardized tool interfaces. For NL2SQL systems, that creates a cleaner boundary between query generation, business semantics and external enrichment—and a clearer checklist for deciding which layer is responsible when an answer is wrong.