Integrations · Market data

Connect MSCI to Well

Bring MSCI index constituents, ESG scores, and risk metrics into Well, joined to the companies you hold or track.

What Well pulls from MSCI

MSCI feeds ESG score, issuer, index constituent into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke MSCI’s access.

From MSCIIn Well
ESG score
Risk signal
Issuer
Entity
Index constituent
Benchmark line
MSCI logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
MSCI → Well

What Well does with your MSCI connection

Connect

Connect MSCI over OAuth (MCP DCR): Well registers a client through MSCI's OAuth Dynamic Client Registration and you approve on MSCI's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings ESG score, issuer, and index constituent in from MSCI on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each MSCI entity into risk signal, entity, and benchmark line, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from MSCI lands in the workspace as risk signal, entity, and benchmark line you can search, chart, and automate.

Questions MSCI unlocks

Ask in plain language. Well answers from your connected MSCI connection, resolved against the rest of your stack.

Ask Well

Ask anything about your MSCI connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your MSCI connection…

Connect MSCI in three steps

  1. 01

    Authorise MSCI via MCP

    From Well's Connections panel, search for MSCI and click Connect. Well discovers MSCI's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on MSCI's side. No client credentials to paste.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.msci.com/index/index-mcp/v1.0/mcp
  2. 02

    Map your entities

    Well's MCP client discovers ESG score, issuer, and index constituent from MSCI that MSCI's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Ask questions in conversation, build records tables, or let agents act on MSCI records. Because MSCI ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.

    • First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical MSCI records happens in the background.

How MSCI stays secure with Well

Well connects to MSCI's MCP server (mcp.msci.com/index/index-mcp/v1.0/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived MSCI secret. Tokens are scoped to the ESG score, issuer, and index constituent MSCI exposes and refreshed server-side. Reads only, Well cannot modify or delete MSCI records.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.msci.com/index/index-mcp/v1.0/mcp
  • Read MSCI records

    Resources the MSCI MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve ESG score, issuer, and index constituent across your stack

    Match identifiers in MSCI against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete MSCI records

    Not granted; MSCI is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store MSCI passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

    refused
Disconnect any time from Well settings or MSCI’s admin panel.

Frequently asked questions about MSCI and Well

From Well, open Connections, find MSCI, and click Connect. Well discovers the OAuth metadata at mcp.msci.com/index/index-mcp/v1.0/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on MSCI's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in ESG score, issuer, and index constituent from MSCI and reshapes each entity into your workspace: ESG score becomes risk signal; issuer becomes entity. Every record arrives with the source identifier preserved, so MSCI stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each MSCI ESG score, index membership, and risk indicator is linked to the matching company in your CRM or portfolio. Ask "what's the MSCI ESG score for our top-10 portfolio companies" and Well returns the breakdown with rating history and peer comparisons.

Each MSCI ESG score is scored against the candidate risk signals in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely risk signal prefilled and the MSCI source attached.

Well combines live MSCI events with periodic reconciliation reads of ESG score, issuer, and index constituent. New rows appear within seconds when MSCI pushes them; periodic reads catch anything a push missed. The first connect backfills history from MSCI in the background.

Open Connections > MSCI in Well and click Disconnect. Well calls MSCI's token revocation endpoint and stops calling MSCI immediately on its side; provider-side propagation to MSCI's admin panel varies by provider. The ESG score, issuer, and index constituent Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

MSCI records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.

MSCI logo

Ready to connect MSCI?

Connect once. Every ESG score, issuer, index constituent from MSCI becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.