Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Simulate how funds may be categorised under the EU's proposed SFDR 2.0 framework; look up funds by name, ISIN or CUSIP.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Clarity AI MCP server connects a simulator for the European Union's proposed SFDR 2.0 fund categories to Claude, ChatGPT and any MCP-compatible agent. Its six read-only tools resolve a fund by name, ISIN or CUSIP and return Clarity AI's modelled view of how that fund might be categorised — evidence for planning, not an official regulatory classification.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Search securities by keyword, ISIN, or CUSIP through the upstream Clarity SFDR demo API.
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'.
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.
Deprecated alias for sfdr20_assess_fund_name. Keep for backward compatibility only. Prefer sfdr20_assess_fund_name for fund names and natural-language requests.
Deprecated alias for sfdr20_check_by_isin. Keep for backward compatibility only. Do not use for fund names or natural-language requests.
Normalize raw SFDR20 flags into category-level assessment evidence.
Read from the server on 2026-08-17, including each tool's own safety annotations.
sfdr20_check and sfdr20_check_by_query are aliases the server itself marks for backward compatibility only.ui:// template is listed, not read. We enumerated the single widget resource on 2026-08-19 and did not fetch its contents, so nothing here describes what it renders.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.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.
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.
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.
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.
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.
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.
documentation value and the MCP host itself. Source for the no-authentication statement, the four-tool vendor list, the three worked examples, the feature descriptions and the troubleshooting entries on endpoint path, ISIN format, empty searches and rate limits. · retrieved 2026-08-17initialize and tools/list handshake against https://clarity-sfdr20-mcp.pro.clarity.ai/mcp — 6 tools with descriptions, input schemas and read-only annotations, returned to an anonymous request (2026-08-17). Source for the tool count, the annotation states, the eight-flag schema, the ISIN pattern, the email argument and the deprecation notices. · retrieved 2026-08-17resources/list and prompts/list against https://clarity-sfdr20-mcp.pro.clarity.ai/mcp — 1 ui:// widget template, text/html;profile=mcp-app, and zero prompts (listed 2026-08-19). The resource was listed only, not read. · retrieved 2026-08-19Connect Clarity AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.