Manufact

LeaderboardBack to leaderboard

app

dark-pulse-iuhle.run.mcp-use.com/mcp

an mcp-use app

View checks

Protocol: MCP 2026-07-28
Server version: 1.0.0
Website: mcp-use.com
Supports: Tools
Resources
Prompts
Logging

Overall score

How is this score calculated?

Last reviewed at Nov 8, 2026, 02:54:10 UTC

Server metadata

Warnings80/100

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

Stable server name

app

10/10Source

Human-readable title

app

10/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.0.0

10/10Source

Public website

Website: mcp-use.com

10/10Source

Scalable or high-resolution icon

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

10/10Source

Server instructions

Usage instructions provided for agents.

20/20Source

Declared capabilities

Supports Tools, Resources, Prompts, Logging.

10/10Source

Server instructions

use show-app to open the app view

Discoverability

0/100

Client listings and public setup information.

mcp.json or server-card.json

Either mcp.json or an MCP Server Card declaring this endpoint passes.

No matching mcp.json manifest or MCP Server Card was found at the checked URLs.

Not foundSource

Setup instructions at MCP URL

The HTML page does not publish connection instructions for this MCP endpoint.

Not foundSource

ChatGPT

No ChatGPT listing has been confirmed yet.

UnverifiedHow to get listed

Claude

No Claude listing has been confirmed yet.

UnverifiedHow to get listed

CursorGrok BotGrok

No Cursor marketplace listing has been confirmed yet.

UnverifiedHow to get listed

Muse

No Muse listing has been confirmed yet.

UnverifiedHow to get listed

4 unverified checks. Unverified checks earn no points until confirmed.

Protocol

Pass100/100

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP modern negotiation succeeded in 1324ms

Source

Tools list returns results

2 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/100

Tool definitions, annotations, and client compatibility.

All tools have OpenAI behavior hints

All tools declare the three OpenAI behavior hints as booleans

Source

Claude Code metadata fits its 2 KB fields

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

Source

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

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

Source

Cursor tool-name budget advisory

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

Observed behavior

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Tool names use valid characters

All tool names use valid characters

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

All tools have a display title

Source

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

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

Declared output schemas have a valid basic structure

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

Source

MCP Apps

Issues71/100

App resources, metadata, and rendering requirements.

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

Tool visibility metadata is valid

All explicit ui.visibility arrays are valid

Source

Views do not request nested iframe domains

No view resource declares frameDomains

Source

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

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

All discovered view resources were inspected

Inspected all 1 discovered view resource(s)

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

79/100

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

show-appTitles 82Descriptions 53Inputs 96Annotations 75Outputs 7176/100

show-app

Title82/100

Show MCP App

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

Description53/100

Display the MCP App starter view

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

Inputs96/100

Input documentation gives an agent enough context to populate the arguments.

appName

Optional title shown in the MCP App card instead of the default

Clear enough to supply this argument.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema71/100

The output schema explains the structured result.

View output schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "message"
  ],
  "properties": {
    "message": {
      "type": "string",
      "description": "Message to display in the MCP App"
    }
  },
  "additionalProperties": false
}

Original tool metadata

{
  "name": "show-app",
  "title": "Show MCP App",
  "description": "Display the MCP App starter view",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "appName": {
        "type": "string",
        "description": "Optional title shown in the MCP App card instead of the default"
      }
    }
  },
  "outputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "message"
    ],
    "properties": {
      "message": {
        "type": "string",
        "description": "Message to display in the MCP App"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

say-helloTitles 89Descriptions 62Inputs 92Annotations 75Outputs 8481/100

say-hello

Title89/100

Say hello

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

Description62/100

Returns a greeting for the Say Hello button demo

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

Inputs92/100

Input documentation gives an agent enough context to populate the arguments.

name

Name to greet

Clear enough to supply this argument.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema84/100

The output schema explains the structured result.

View output schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "greeting"
  ],
  "properties": {
    "greeting": {
      "type": "string",
      "description": "Greeting to display"
    }
  },
  "additionalProperties": false
}

Original tool metadata

{
  "name": "say-hello",
  "title": "Say hello",
  "description": "Returns a greeting for the Say Hello button demo",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Name to greet"
      }
    }
  },
  "outputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "greeting"
    ],
    "properties": {
      "greeting": {
        "type": "string",
        "description": "Greeting to display"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "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.

01Say helloReturns a greeting for the Say Hello button demo
02Show MCP AppDisplay the MCP App starter view

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

Test your MCP in Cloud Book a test call

FAQ

app setup, tools, quality score, publishing readiness, and alternatives.

How do I add app to Claude, ChatGPT, or Cursor?

Add app 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://dark-pulse-iuhle.run.mcp-use.com/mcp.

Is app MCP ready for ChatGPT and Claude?

As of November 8, 2026, app scores 91/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 app's MCP tool documentation?

As of November 8, 2026, app scores 79/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 2 of 2 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

How can app improve its MCP documentation?

show-app is the lowest-scoring reviewed tool at 76/100. Describe the concrete operation and its scope instead of restating the tool name. 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

LeaderboardBack to leaderboardLeaderboardBack to leaderboard

Opening report…

Loading report overview

Server metadata

Loading server metadata

Discoverability

Loading discoverability

Protocol

Loading protocol

Tools

Loading tools

MCP Apps

Loading mcp apps

Tool documentation quality

Loading tool documentation quality

Title82/100

Show MCP App

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

Description53/100

Display the MCP App starter view

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

Inputs96/100

Input documentation gives an agent enough context to populate the arguments.

appName

Optional title shown in the MCP App card instead of the default

Clear enough to supply this argument.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema71/100

The output schema explains the structured result.

View output schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "message"
  ],
  "properties": {
    "message": {
      "type": "string",
      "description": "Message to display in the MCP App"
    }
  },
  "additionalProperties": false
}

Original tool metadata

{
  "name": "show-app",
  "title": "Show MCP App",
  "description": "Display the MCP App starter view",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "appName": {
        "type": "string",
        "description": "Optional title shown in the MCP App card instead of the default"
      }
    }
  },
  "outputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "message"
    ],
    "properties": {
      "message": {
        "type": "string",
        "description": "Message to display in the MCP App"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

Manufact

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title82/100

Description53/100

Inputs96/100

Annotations75/100

Output schema71/100

Title89/100

Description62/100

Inputs92/100

Annotations75/100

Output schema84/100

Put your MCP to the test

FAQ

Not your MCP?

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool documentation quality

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title82/100

Description53/100

Inputs96/100

Annotations75/100

Output schema71/100

Title89/100

Description62/100

Inputs92/100

Annotations75/100

Output schema84/100

Put your MCP to the test

FAQ

Not your MCP?

Tool documentation quality

Tool documentation quality