Clarity AI

Name: Clarity AI MCP Server
Availability: InStock
Author: Clarity AI

Finance6 toolsNo Auth Required

Simulate how investment funds may be categorised under the European Commission's proposed SFDR 2.0 framework. Look up funds by name, ISIN or CUSIP. 6 tools, all read-only, no sign-in.

Verified connector

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

Connection checked by Agentman on 17 August 2026.

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

Connect Clarity AI via MCP

https://clarity-sfdr20-mcp.pro.clarity.ai/mcp

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

Clarity AI Tools & Capabilities (6)

search_securitiesRead-only

Search securities by keyword, ISIN, or CUSIP through the upstream Clarity SFDR demo API.

sfdr20_assess_fund_nameRead-only

Preferred for fund names, partial names, and natural-language requests. Resolve a fund from free-text (for example S&P 500 or Nordea 1 Global Climate and Environment), then run the SFDR20 check and return an interpreted assessment. Example: use this for 'Show the SFDR 2.0 category assessment evidence for Nordea 1 Global Climate and Environment Fund'.

sfdr20_check_by_isinRead-only

Use only when the user already provided an explicit ISIN. Do not use for fund names, partial names, or natural-language fund requests; use sfdr20_assess_fund_name instead.

sfdr20_check_by_queryRead-only

Deprecated alias for sfdr20_assess_fund_name. Keep for backward compatibility only. Prefer sfdr20_assess_fund_name for fund names and natural-language requests.

sfdr20_checkRead-only

Deprecated alias for sfdr20_check_by_isin. Keep for backward compatibility only. Do not use for fund names or natural-language requests.

interpret_sfdr20_resultRead-only

Normalize raw SFDR20 flags into category-level assessment evidence.

Read from the server on 2026-08-17, including each tool's own safety annotations.

Limits

The output is simulated, not official. Clarity AI's server page describes the results as simulated category assessment evidence based on its proprietary modelling and estimated figures. Its troubleshooting adds that assessments are subject to change as the framework evolves, and its own description calls this "a live tool that will evolve".
The regulation is a proposal, not law. COM(2025) 841 was published on 20 November 2025 and states it shall apply 18 months after entry into force, which has not occurred. No fund has a binding SFDR 2.0 category today, and the criteria the connector models may change before adoption.
Not advice, and Clarity AI says so. Its terms and conditions state the site is "not a source of advice", that nothing may be interpreted as the provision of financial, commercial or strategic advice, and that Clarity AI and its agents are not to be deemed professionals rendering auditing, investing, financial, accounting or legal services. It recommends seeking expert professional advice before deciding anything in these matters.
No accuracy guarantee. The same terms state Clarity AI does not guarantee its information is free of "error or defect" or that it fits any particular purpose, and it accepts no responsibility for loss arising from a lack of accuracy or completeness. This is the vendor's own wording, not our characterisation.
Coverage is undocumented. No universe size, fund count, jurisdiction list or data-vintage date is published. The tool descriptions call the upstream a demo API.
Funds only, and EU rules only. Every tool addresses fund-level SFDR categorisation. There is no company-level ESG score, no portfolio holdings tool and no non-EU framework here.
Two of six tools are deprecated. sfdr20_check and sfdr20_check_by_query are aliases the server itself marks for backward compatibility only.
Rate limited per IP. Clarity AI's troubleshooting documents per-IP rate limits and advises waiting or reducing request frequency. No numeric threshold is published.
We did not exercise any tool. Our check was a read-only initialize and tools/list handshake. Everything above comes from the server's own tool descriptions, Clarity AI's published pages and the Commission's proposal text — not from calling anything.

Frequently asked questions

Does the Clarity AI SFDR 2.0 MCP server need an account or API key?

No. Clarity AI's server page states the service does not require authentication, and our anonymous handshake on 2026-08-17 returned all six tool definitions without a credential. Two tools do accept an optional email argument, and the ISIN tools require it, but no sign-in, OAuth flow or API key is involved at any point.

Is a Clarity AI SFDR 2.0 result an official regulatory classification?

No. Clarity AI describes the output as simulated category assessment evidence based on its own modelling of the November 2025 proposal, not an official categorisation. The European Commission proposal was published on 20 November 2025 and is not yet law, so no fund has a binding SFDR 2.0 category to report. Treat results as preparation, not compliance.

What do the Article 7, 8 and 9 flags in the Clarity AI connector mean?

They map to the three product categories in the Commission's proposal: Article 7 is transition, Article 8 is ESG basics and Article 9 is sustainable. Each category carries both contribution criteria and exclusions, which is why every article in the schema has a paired contribution and exclusion flag the connector reports separately.

Which funds can the Clarity AI SFDR 2.0 connector look up?

Any security its upstream search resolves from a keyword, ISIN or CUSIP. Clarity AI publishes no coverage list, universe size or data-vintage date for this server, so we cannot state which funds are present. The tool descriptions call the upstream a demo API, and a fund search returning nothing may mean absent coverage rather than an invalid query.

Why does the Clarity AI connector reject my ISIN?

The ISIN failed the server's format check before any lookup ran. Clarity AI's troubleshooting states an ISIN must be exactly twelve characters: two uppercase letters, nine alphanumeric characters and one final digit. The live schema enforces that same pattern as a regular expression, so a malformed identifier is refused by the schema rather than searched for.

Why are the Clarity AI tools not appearing in Claude?

The configured URL is probably the root address rather than the MCP endpoint. Clarity AI's troubleshooting says to confirm the endpoint path ends in /mcp, then re-save the connector and reload Claude. The root URL serves the human-readable server page instead of the protocol endpoint, so a client pointed at it discovers no tools.