Manufact

clarity-sfdr20-mcp

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

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.

Protocol: MCP 2025-11-25
Server version: 0.1.1
Supports: Tools
Resources

Overall score

Last reviewed at Oct 6, 2026, 14:18:16 UTC

Server metadata

3 of 8 fields30/1002.4 / 8 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

clarity-sfdr20-mcp

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 0.1.1

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools, Resources.

10/10Source

Protocol

Pass100/10016 / 16 pts

Connection, authentication, and protocol compatibility.

Resources list responds

1 resource(s) returned

Source

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 617ms

Source

Tools list returns results

6 tool(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Pass100/10024 / 24 pts

Tool definitions, annotations, and client compatibility.

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

All tools have descriptions

All tools have non-empty descriptions

All tools have OpenAI behavior hints

All tools declare the three OpenAI behavior hints as booleans

Source

Tool names use valid characters

All tool names use valid characters

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

All tools have a display title

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Issues68/10013.6 / 20 pts

App resources, metadata, and rendering requirements.

View resource envelope is valid

All view resources are readable and use ui:// with a supported MCP Apps HTML MIME type

Tool-linked resource URI is readable

All tool-linked resource URIs are readable

Source

All discovered view resources were inspected

Inspected all 1 discovered view resource(s)

Source

Tool invocation metadata present

4 tool(s) missing openai/toolInvocation metadata

How to fix: For tools that render a UI resource, add openai/toolInvocation with string fields invoking and invoked (present-tense labels shown while the tool runs and after it finishes, e.g. "Searching…" / "Searched").

warningChatGPT

Source

View resource metadata complete

1 resource(s) have incomplete metadata

How to fix: Use a ui:// URI and text/html;profile=mcp-app. For mcp-use servers, set the widget description in widgetMetadata; other stacks can use _meta.ui.widgetDescription or the OpenAI compatibility alias.

warningChatGPTClaude.ai

Source

Declared domains respond

All declared domains are reachable

CSP metadata covers literal external origins

All statically detectable external origins are declared in CSP metadata

Source

View resources declare a domain

1 ChatGPT UI domain issue(s) found

How to fix: For ChatGPT submission, set one exact HTTPS origin such as "https://app.example.com" on every view via _meta.ui.domain (or openai/widgetDomain). Paths are not valid and all views in one app must share the origin.

errorChatGPT

Source

Tool visibility metadata is valid

All explicit ui.visibility arrays are valid

Source

Tool documentation quality

6 tools reviewed50/10016 / 32 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

search_securitiesTitles 100Descriptions 68Inputs 0Annotations 75Outputs 052/100

Title100/100

Search Securities

The title clearly communicates the tool’s action and subject. Keep it concise.

Description68/100

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

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

query

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Search Securities",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_securities",
  "title": "Search Securities",
  "description": "Search securities by keyword, ISIN, or CUSIP through the upstream Clarity SFDR demo API.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "Search Securities",
    "readOnlyHint": true,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

sfdr20_assess_fund_nameTitles 95Descriptions 89Inputs 0Annotations 75Outputs 057/100

Title95/100

SFDR 2.0 Check by Fund Name

The title clearly communicates the tool’s action and subject. Keep it concise.

Description89/100

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

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

query

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "SFDR 2.0 Check by Fund Name",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "sfdr20_assess_fund_name",
  "title": "SFDR 2.0 Check by Fund Name",
  "description": "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'.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "SFDR 2.0 Check by Fund Name",
    "readOnlyHint": true,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

sfdr20_check_by_isinTitles 97Descriptions 68Inputs 0Annotations 75Outputs 052/100

Title97/100

SFDR 2.0 Check by ISIN

The title clearly communicates the tool’s action and subject. Keep it concise.

Description68/100

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.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

isin

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "SFDR 2.0 Check by ISIN",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "sfdr20_check_by_isin",
  "title": "SFDR 2.0 Check by ISIN",
  "description": "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.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "SFDR 2.0 Check by ISIN",
    "readOnlyHint": true,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

sfdr20_check_by_queryTitles 83Descriptions 68Inputs 0Annotations 75Outputs 048/100

Title83/100

SFDR 2.0 Check by Fund Name (Legacy Alias)

Shorten the title to an action and subject; move usage details into the description.

Description68/100

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

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

query

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "SFDR 2.0 Check by Fund Name (Legacy Alias)",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "sfdr20_check_by_query",
  "title": "SFDR 2.0 Check by Fund Name (Legacy Alias)",
  "description": "Deprecated alias for sfdr20_assess_fund_name. Keep for backward compatibility only. Prefer sfdr20_assess_fund_name for fund names and natural-language requests.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "SFDR 2.0 Check by Fund Name (Legacy Alias)",
    "readOnlyHint": true,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

sfdr20_checkTitles 79Descriptions 59Inputs 0Annotations 75Outputs 044/100

Title79/100

SFDR 2.0 Check by ISIN (Legacy Alias)

Shorten the title to an action and subject; move usage details into the description.

Description59/100

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

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

isin

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "SFDR 2.0 Check by ISIN (Legacy Alias)",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "sfdr20_check",
  "title": "SFDR 2.0 Check by ISIN (Legacy Alias)",
  "description": "Deprecated alias for sfdr20_check_by_isin. Keep for backward compatibility only. Do not use for fund names or natural-language requests.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "SFDR 2.0 Check by ISIN (Legacy Alias)",
    "readOnlyHint": true,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

interpret_sfdr20_resultTitles 88Descriptions 65Inputs 0Annotations 75Outputs 048/100

Title88/100

Interpret SFDR 2.0 Result

The title clearly communicates the tool’s action and subject. Keep it concise.

Description65/100

Normalize raw SFDR20 flags into category-level assessment evidence.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ARTICLE_7_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_7_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_8_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_8_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_9_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_9_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

MIXED_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

MIXED_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Interpret SFDR 2.0 Result",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "interpret_sfdr20_result",
  "title": "Interpret SFDR 2.0 Result",
  "description": "Normalize raw SFDR20 flags into category-level assessment evidence.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "Interpret SFDR 2.0 Result",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01SFDR 2.0 Check by Fund NamePreferred for fund names, partial names, and natural-language requests.
02Search SecuritiesSearch securities by keyword, ISIN, or CUSIP through the upstream Clarity SFDR demo API.
03Interpret SFDR 2.0 ResultNormalize raw SFDR20 flags into category-level assessment evidence.
04SFDR 2.0 Check by Fund Name (Legacy Alias)Deprecated alias for sfdr20_assess_fund_name.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

About this server

Overview

Author: Clarity AI
Verification: partner
Auth: None (public endpoint)
Category: Finance
Works with: claude
claude-api
claude-code
Docs: Documentation

Tools (4)

search_securitiessfdr20_checksfdr20_check_by_queryinterpret_sfdr20_result

FAQ

clarity-sfdr20-mcp setup, tools, quality score, publishing readiness, and alternatives.

How do I add clarity-sfdr20-mcp to Claude, ChatGPT, or Cursor?

Add clarity-sfdr20-mcp to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://clarity-sfdr20-mcp.pro.clarity.ai/mcp.

Is clarity-sfdr20-mcp MCP ready for ChatGPT and Claude?

As of October 6, 2026, clarity-sfdr20-mcp scores 90/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is clarity-sfdr20-mcp's MCP tool documentation?

As of October 6, 2026, clarity-sfdr20-mcp scores 50/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 6 of 6 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What tools does the clarity-sfdr20-mcp MCP server provide?

clarity-sfdr20-mcp provides these MCP tools: search_securities, sfdr20_check, sfdr20_check_by_query, and interpret_sfdr20_result.

What are the best alternatives to clarity-sfdr20-mcp?

As of October 20, 2026, alternatives to clarity-sfdr20-mcp in financial-services on the Manufact MCP leaderboard include Contract-Factory — Sociétés & SIREN, Coverage Cat Insurance, Kavara Kirk, Perps Pulse, and CeylonCharts.

Does clarity-sfdr20-mcp MCP require authentication?

clarity-sfdr20-mcp does not require authentication. It is a public MCP endpoint you can connect without logging in.

How can clarity-sfdr20-mcp improve its MCP documentation?

sfdr20_check is the lowest-scoring reviewed tool at 44/100. 0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Who develops clarity-sfdr20-mcp?

clarity-sfdr20-mcp is developed by Clarity AI. It is listed as partner on the Claude connector directory.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…

Title88/100

Interpret SFDR 2.0 Result

The title clearly communicates the tool’s action and subject. Keep it concise.

Description65/100

Normalize raw SFDR20 flags into category-level assessment evidence.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ARTICLE_7_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_7_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_8_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_8_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_9_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

ARTICLE_9_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

MIXED_EXCLUSION

Not provided

Missing description. Explain what this value means and how to supply it.

MIXED_CONTRIBUTION

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Interpret SFDR 2.0 Result",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "interpret_sfdr20_result",
  "title": "Interpret SFDR 2.0 Result",
  "description": "Normalize raw SFDR20 flags into category-level assessment evidence.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "title": "Interpret SFDR 2.0 Result",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

Manufact

Server metadata

Protocol

Tools

MCP Apps

Tool documentation quality

Title100/100

Description68/100

Inputs0/100

Annotations75/100

Output schema0/100

Title95/100

Description89/100

Inputs0/100

Annotations75/100

Output schema0/100

Title97/100

Description68/100

Inputs0/100

Annotations75/100

Output schema0/100

Title83/100

Description68/100

Inputs0/100

Annotations75/100

Output schema0/100

Title79/100

Description59/100

Inputs0/100

Annotations75/100

Output schema0/100

Title88/100

Description65/100

Inputs0/100

Annotations75/100

Output schema0/100

Put your MCP to the test

About this server

Overview

Related MCP servers

FAQ

Not your MCP?

Server metadata

Protocol

Tools

MCP Apps

Tool documentation quality

Title100/100

Description68/100

Inputs0/100

Annotations75/100

Output schema0/100

Title95/100

Description89/100

Inputs0/100

Annotations75/100

Output schema0/100

Title97/100

Description68/100

Inputs0/100

Annotations75/100

Output schema0/100

Title83/100

Description68/100

Inputs0/100

Annotations75/100

Output schema0/100

Title79/100

Description59/100

Inputs0/100

Annotations75/100

Output schema0/100

Title88/100

Description65/100

Inputs0/100

Annotations75/100

Output schema0/100

Put your MCP to the test

About this server

Overview