Assess how investment funds may be classified under the European Commission's proposed SFDR 2.0 framework — directly from Claude. Search funds by name, ISIN, or CUSIP and get simulated Article classifications based on Clarity AI's regulatory disclosure data and proprietary modelling of the November 2025 proposal. Ideal for ESG analysts, portfolio managers, and compliance teams preparing for the regulatory transition before final rules are published. This is a live tool that will evolve as we learn more from ongoing EU discussions and guidance.

What we measured

Over the last 30 days we probed this MCP server 23 times on 22 days; it answered 23 (100%). Median response 474 ms, 95th percentile 555 ms.

When we called tools/list it returned 6 tools, including search_securities, sfdr20_assess_fund_name, sfdr20_check_by_isin, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 42% and higher on readiness than 80%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (6)

As returned by the server's own tools/list when we called it.

search_securities: Search securities by keyword, ISIN, or CUSIP through the upstream Clarity SFDR demo API.
sfdr20_assess_fund_name: 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 Enviro…
sfdr20_check_by_isin: 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_na…
sfdr20_check_by_query: 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_check: Deprecated alias for sfdr20_check_by_isin. Keep for backward compatibility only. Do not use for fund names or natural-language requests.
interpret_sfdr20_result: Normalize raw SFDR20 flags into category-level assessment evidence.

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 88.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (555 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	23/23 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 6 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (555 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-12.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness: Higher than 80% of peers; This listing 86 · peer median 81
Latency: Faster than 42% of peers; This listing 428 ms · peer median 349 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

Site rank (Tranco): #450,863 of the top 1M; clarity.ai · list of 2026-11-12

Listed in

Directories this entry was found in.

agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

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

JSON-RPC initialize probe

curl -X POST https://clarity-sfdr20-mcp.pro.clarity.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

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

Listed at (agenstry)

https://agenstry.com/mcp/ai.clarity/sfdr20-mcp