Manufact

Back to submission

calm-steel-fqshc.run.mcp-use.com

calm-steel-fqshc.run.mcp-use.com/mcp

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

Overall score

Last reviewed at Oct 7, 2026, 21:19:35 UTC

Server metadata

5 of 8 fields50/1004 / 8 pts

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

Stable server name

blossom-hill

10/10Source

Human-readable title

Blossom Hill

10/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 0.1.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

1 icon advertised, including a scalable or high-resolution asset.

10/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.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 930ms

Source

Tools list returns results

1 tool(s) returned

Source

Resources list responds

1 resource(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.

All tools have descriptions

All tools have non-empty descriptions

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 tool names are within 64 characters

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

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

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

ChatGPT tool names are unique

All tool names are unique

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 MCP uniqueness guidance

All tool names are unique

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

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.

All discovered view resources were inspected

Inspected all 1 discovered view resource(s)

Source

Tool invocation metadata present

1 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 envelope is valid

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

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 v1, use widgetMetadata.metadata.widgetDescription; for v2, use the bound tool's view.description. The current description check reads _meta.ui.widgetDescription or _meta["openai/widgetDescription"] on resource contents or linked tools, not resource.description. Consequently, v2 view.description alone may leave this warning: report the checker compatibility gap instead of adding unsupported v1 fields or claiming the warning is fixed.

warningChatGPTClaude.ai

Source

Tool-linked resource URI is readable

All tool-linked resource URIs are readable

Source

Tool visibility metadata is valid

All explicit ui.visibility arrays are valid

Source

Declared domains respond

All declared domains are reachable

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

CSP metadata covers literal external origins

All statically detectable external origins are declared in CSP metadata

Source

Tool documentation quality

1 tools reviewed68/10021.8 / 32 pts

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

blossom.homeTitles 51Descriptions 67Inputs 100Annotations 100Outputs 068/100

Title51/100

Blossom Hill

Align the title with the capability actually described by this tool.

Description67/100

Open the Blossom Hill homepage and its one fictional upcoming café event.

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

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": 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": "blossom.home",
  "title": "Blossom Hill",
  "description": "Open the Blossom Hill homepage and its one fictional upcoming café event.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "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.

01Blossom HillOpen the Blossom Hill homepage and its one fictional upcoming café event.

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

Test your MCP in Cloud Book a test call

FAQ

calm-steel-fqshc.run.mcp-use.com setup, tools, quality score, publishing readiness, and alternatives.

How do I add calm-steel-fqshc.run.mcp-use.com to Claude, ChatGPT, or Cursor?

Add calm-steel-fqshc.run.mcp-use.com 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://calm-steel-fqshc.run.mcp-use.com/mcp.

Is calm-steel-fqshc.run.mcp-use.com MCP ready for ChatGPT and Claude?

As of October 7, 2026, calm-steel-fqshc.run.mcp-use.com 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 calm-steel-fqshc.run.mcp-use.com's MCP tool documentation?

As of October 7, 2026, calm-steel-fqshc.run.mcp-use.com scores 68/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 1 of 1 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

How can calm-steel-fqshc.run.mcp-use.com improve its MCP documentation?

blossom.home is the lowest-scoring reviewed tool at 68/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

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…