_ registry / mcp streamable-http · checked 2h ago

clarity-sfdr20-mcp

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

Registry code: 0a5dcad7c71b8daf

api record

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.

from a public catalogue that lists it, not from the operator

endpoint
https://clarity-sfdr20-mcp.pro.clarity.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is clarity-sfdr20-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is clarity-sfdr20-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does clarity-sfdr20-mcp have?
6 tools: sfdr20_check, sfdr20_check_by_isin, sfdr20_check_by_query, interpret_sfdr20_result, search_securities, sfdr20_assess_fund_name.
Is clarity-sfdr20-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
135ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 315 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
security & compliance compliance & regulation
used for
  • check a fund against sfdr 2.0 categories
  • search securities by isin
  • interpret sfdr assessment flags
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • sfdr20_check reads unknown 17h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "isin",
    "email"
  ],
  "properties": {
    "isin": {
      "type": "string",
      "pattern": "^[A-Z]{2}[A-Z0-9]{9}[0-9]$"
    },
    "email": {
      "type": "string",
      "format": "email"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • sfdr20_check_by_isin reads unknown 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "isin",
    "email"
  ],
  "properties": {
    "isin": {
      "type": "string",
      "pattern": "^[A-Z]{2}[A-Z0-9]{9}[0-9]$"
    },
    "email": {
      "type": "string",
      "format": "email"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • sfdr20_check_by_query reads unknown 17h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email"
    },
    "query": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • interpret_sfdr20_result reads unknown 9h ago

    Normalize raw SFDR20 flags into category-level assessment evidence.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ARTICLE_7_EXCLUSION",
    "ARTICLE_7_CONTRIBUTION",
    "ARTICLE_8_EXCLUSION",
    "ARTICLE_8_CONTRIBUTION",
    "ARTICLE_9_EXCLUSION",
    "ARTICLE_9_CONTRIBUTION",
    "MIXED_EXCLUSION",
    "MIXED_CONTRIBUTION"
  ],
  "properties": {
    "MIXED_EXCLUSION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "MIXED_CONTRIBUTION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "ARTICLE_7_EXCLUSION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "ARTICLE_8_EXCLUSION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "ARTICLE_9_EXCLUSION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "ARTICLE_7_CONTRIBUTION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "ARTICLE_8_CONTRIBUTION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    },
    "ARTICLE_9_CONTRIBUTION": {
      "enum": [
        0,
        1
      ],
      "type": "number"
    }
  },
  "additionalProperties": false
}
    arguments 73 lines
  • search_securities reads unknown 9h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email"
    },
    "query": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • sfdr20_assess_fund_name reads unknown 9h ago

    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'.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email"
    },
    "query": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0a5dcad7c71b8daf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0a5dcad7c71b8daf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0a5dcad7c71b8daf/badge.svg)](https://brick.blue/agent/0a5dcad7c71b8daf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.