MyRace AI

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 1885ms

Tools list returns results

10 tool(s) returned

Resources list responds

4 resource(s) returned

Server declares tools capability

Server declares tools capability in initialize response

All tools have descriptions

All tools have non-empty descriptions

All tools have OpenAI behavior hints

10 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

Tool names use valid characters

All tool names use valid characters

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Tool names follow MCP uniqueness guidance

All tool names are unique

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

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

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Tool invocation metadata present

3 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").

Tool-linked resource URI is readable

All tool-linked resource URIs are readable

Tool visibility metadata is valid

All explicit ui.visibility arrays are valid

View resource metadata complete

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

All discovered view resources were inspected

Inspected all 3 discovered view resource(s)

View resource envelope is valid

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

CSP metadata covers literal external origins

All statically detectable external origins are declared in CSP metadata

Declared domains respond

All declared domains are reachable

View resources declare a domain

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

Claude Code metadata fits its 2 KB fields

1 metadata field(s) exceed Claude Code's 2 KB truncation point

How to fix: Keep each tool description and the server instructions field at or below 2 KB, and put critical guidance first.

Claude tool names are within 64 characters

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

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

All tools have a display title

All tools have a display title

ChatGPT tool names are unique

All tool names are unique

Cursor tool-name budget advisory

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

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas