LSEG

Name: LSEG MCP Server
Availability: InStock
Author: LSEG

Finance20 tools

LSEG Financial Analytics exposed over MCP. Most of these 20 tools do not fetch a stored quote — they value an instrument from a model, with Greeks, curves and vol surfaces. Access needs an LSEG Financial Analytics licence, and three published tool lists disagree with each other.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect LSEG via MCP

https://api.analytics.lseg.com/lfa/mcp/server-cl

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

LSEG Tools & Capabilities (20)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The documentation Anthropic links is a marketing page, not a developer doc. lseg.com/en/solutions/ai-finance-solutions/anthropic carries positioning, executive quotes and a sales form. It names no tool, no endpoint, no authentication method and no entitlement mechanism. A reader following that link alone learns nothing operational.
LSEG's real MCP developer documentation exists and is behind a login wall. We located it via developers.lseg.com/sitemap.xml at the Financial Analytics API catalogue, and the page returns "Please sign in to explore content on this page". Everything technical on this page therefore comes from LSEG's public GitHub repository, LSEG's LSEG-published Microsoft connector reference, and Anthropic's tutorial — not from LSEG's own MCP docs, which we could not read.
Three published tool lists disagree, in both directions. 20 in the directory, 17 at Microsoft, 22 in LSEG's repository; 15 common, 26 in union. At least three names have competing spellings. We could not determine which the live server accepts.
We could not verify any tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no live schemas were readable and no readOnlyHint or destructiveHint annotations were available. No tool on this page is annotated; none should be assumed safe on its name.
Entitlement scoping is undocumented. LSEG states entitlements are enforced and metered but never says whether an unentitled user sees fewer tools or sees the same tools return narrowed data. The second shape is the dangerous one, because an incomplete answer looks like a complete one. Establish which applies with LSEG before relying on completeness.
Valuations are model output, and the model's assumptions are yours to get right. Day-count convention, curve construction, discounting choice and market-data vintage all move the number. An agent composing several of these calls can produce a well-formatted wrong answer without any error surfacing.
LSEG disclaims accuracy and reliance, and we carry that unsoftened. LSEG states its content "does not seek to constitute advice of any nature and no reliance should be placed upon statements contained herein", provides information "as is" without warranty of any kind, and expressly disclaims warranties including accuracy, completeness, reliability and fitness for a particular purpose. It cites the possibility of human and mechanical error. This catalogue offers no investment or financial advice of any kind, and describes what these tools do rather than what to do with their output.
No scopes are published on the resource, and the authorization server's three are identity-only. openid, profile and email say nothing about which market data a token may reach. There is no scope-level signal of entitlement to inspect before connecting.
PKCE is not advertised. code_challenge_methods_supported is absent from the RFC 8414 metadata.
Access is enterprise-gated. No free tier, no self-service signup, no public pricing. An individual cannot meaningfully evaluate this connector without an LSEG commercial relationship.
Prompts are unconfirmed. Anthropic's snapshot lists none, and the gated endpoint blocked our own check. Absence in a snapshot is not evidence the server serves none.
We did not read any LSEG data licensing agreement. What you may do with data pulled through this connector is governed by your contract with LSEG, which LSEG explicitly directs users to. Nothing here is legal advice.

Frequently asked questions

Does the LSEG MCP server calculate valuations or return published prices?

It calculates. LSEG's own documentation leads nearly every pricing tool with the verb Calculate, and LSEG describes the underlying Financial Analytics service as running on Adfin, Price-It and YieldBook quantitative models. So option_value returns a model valuation with Greeks, not a dealer quote. The inputs, curve and convention you supply change the number that comes back.

What do the qa_ tools in the LSEG MCP server cover?

The qa prefix means Quantitative Analytics, and those tools retrieve stored data rather than compute it. LSEG's plugin repository groups qa_ibes_consensus, qa_company_fundamentals and qa_macroeconomic under that heading. IBES is LSEG's analyst-estimates database, collecting sell-side forecasts since 1976. The other two cover reported company financials and historical macroeconomic indicators worldwide.

Do I need an LSEG subscription to use the LSEG MCP server?

Yes. Microsoft's LSEG-published connector reference lists access to the LSEG Financial Analytics system as a prerequisite, and LSEG's own plugin repository requires data entitlements for the relevant product offerings. Anthropic's tutorial says to contact LSEG for access. This is an enterprise licensed-data product, not something an individual signs up for online.

How many tools does the LSEG MCP server have?

Anthropic's directory snapshot lists 20, and this page renders those 20. But two LSEG-authored sources disagree with it and with each other: Microsoft's connector reference documents 17 and LSEG's plugin repository documents 22. Only 15 names appear in all three lists. The union across the three sources is 26 distinct names.

What OAuth scopes does the LSEG MCP server request?

None are published. LSEG's protected-resource descriptor omits the scopes_supported field entirely, naming only the resource and its authorization server. The authorization server at login.ciam.refinitiv.com advertises just openid, profile and email — standard OpenID Connect claims that carry no LSEG product entitlement. Data permissions are enforced by licence, not by scope.

Does LSEG say its MCP valuations are investment advice?

The opposite. LSEG states its published content does not seek to constitute advice of any nature and that no reliance should be placed on it, and it disclaims warranties of accuracy, completeness and fitness for a particular purpose. LSEG also directs users to their own data licensing agreement for what they may do with the output.

Is the server-cl suffix in the LSEG MCP URL a per-client identifier?

It behaves like a prefix match, not a client identity. We probed variants on 2026-08-19: server-cl2 and server-cll both returned challenges naming server-cl, while unrelated suffixes fell back to the bare path. So the route matches a prefix rather than resolving distinct customers. Anthropic's own tutorial documents the bare URL instead.

Sources

Anthropic connector directory — https://claude.ai/directory/5f26bc32-8582-4df7-ab88-19c507f8505b (snapshot 2026-08-16; the canonical 20 tool names, "Read" permissions, no prompts, partner tier, the server-cl endpoint and the server_label field carrying the bare /lfa/mcp form) · retrieved 2026-08-16
LSEG and Anthropic partnership page — https://www.lseg.com/en/solutions/ai-finance-solutions/anthropic (fetched 2026-08-19; the documentation URL Anthropic's directory carries. A marketing page: it names Workspace and Financial Analytics as the licensed products and Claude for Financial Services as the audience, but no tool, endpoint or auth detail. The .md suffix form returns a 404 HTML shell) · retrieved 2026-08-19
LSEG official plugin repository — https://github.com/LSEG-API-Samples/lseg-claude-plugin (fetched 2026-08-19; README.md and CONNECTORS.md. Source of the "LFA MCP Server" name, the 22-tool list, the Quantitative Analytics expansion of qa, the SABR attribution, and the two stated requirements: MCP Server credentials and data entitlements) · retrieved 2026-08-19
Microsoft Learn, LSEG connector reference — https://learn.microsoft.com/en-us/connectors/lseg/ (fetched 2026-08-19; publisher recorded as LSEG Financial Analytics with an mcp-support lseg.com contact. Source of the 17-tool list, the per-tool "Calculate" descriptions, the "Access to LSEG Financial Analytics system" prerequisite, and the 100-calls-per-60-seconds throttle) · retrieved 2026-08-19
Anthropic, "Using LSEG for financial market data analysis" — https://academy.claude.com/tutorials/using-lseg-for-financial-market-data-analysis (fetched 2026-08-19, via two 301 redirects from support.claude.com; source of "contact LSEG to get access", the org-owner admin flow, and the bare https://api.analytics.lseg.com/lfa/mcp endpoint form) · retrieved 2026-08-19
LSEG Financial Analytics API catalogue — https://developers.lseg.com/en/api-catalog/lseg-financial-analytics/lseg-financial-analytics-apis (fetched 2026-08-19; the cross-asset coverage list, the Adfin, Price-It and YieldBook model attribution, and the statement that users may modify calculation parameters or supply their own data) · retrieved 2026-08-19
LSEG Financial Analytics MCP documentation — https://developers.lseg.com/en/api-catalog/lseg-financial-analytics/lseg-financial-analytics-apis/mcp (fetched 2026-08-19; login-gated — returns "Please sign in to explore content on this page". Located via the developer sitemap, not guessed. No technical content readable) · retrieved 2026-08-19
LSEG, "Scaling AI in Financial Services with LSEG's Trusted AI Ready Content and MCP" — https://www.lseg.com/en/insights/scaling-ai-financial-services-with-lseg-trusted-ai-ready-content-mcp (fetched 2026-08-19; source of the deterministic-calculation framing, the entitlement and metering statements, the direction to the user's own data licensing agreement, and the legal disclaimer quoted in Limits) · retrieved 2026-08-19
A-Team Insight, "Now the MCP Layer is Commoditised, Are Entitlements the Next Challenge?" — https://a-teaminsight.com/blog/now-the-mcp-layer-is-commoditised-are-entitlements-the-next-challenge/ (fetched 2026-08-19; independent observation that major content vendors have not been explicit about how user-level entitlements propagate through their MCP servers) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor — https://api.analytics.lseg.com/.well-known/oauth-protected-resource/lfa/mcp/server-cl (fetched 2026-08-19; the path-insert form named by the www-authenticate challenge. 200, 106 bytes, two fields, no scopes_supported. The root form returns a 404 gateway error; the path-append form returns a 401 token challenge) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://login.ciam.refinitiv.com/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer, the three OpenID Connect scopes, eleven grant types, the registration endpoint, and the absence of code_challenge_methods_supported) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an anonymous initialize POST to https://api.analytics.lseg.com/lfa/mcp/server-cl returns HTTP 401 with www-authenticate: Bearer realm="MCP Server", resource_metadata="https://api.analytics.lseg.com/.well-known/oauth-protected-resource/lfa/mcp/server-cl". Prefix-matching behaviour established by probing documented-path variants only · retrieved 2026-08-19
www.lseg.com/robots.txt and developers.lseg.com/robots.txt (both fetched 2026-08-19; allow all user agents with path exclusions for layout, form and error routes. No Content-Signal axes on either. No llms.txt is published — www.lseg.com/llms.txt returns a 404 HTML page) · retrieved 2026-08-19
LSEG I/B/E/S Estimates — https://www.lseg.com/en/data-analytics/financial-data/company-data/ibes-estimates (fetched 2026-08-19; IBES as LSEG's analyst-estimates database, with US history from 1976) · retrieved 2026-08-19