Skip to content
MCPSTAMP
MCP server report

MRC Data MCP server

ai.meacheal/mrc-data

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 74 of 100 (grade C), higher than 19.5% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude and MCP Registry. Not ready for ChatGPT and Gemini.

Measured facts

Score
74C
Sign-in
API key or other
Tools listed
20
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728) and Authorization server metadata (RFC 8414 / OIDC).
Gemini Connected Apps Not ready Blocked by Sign-in method the store supports (OAuth or none) and Authorization server metadata (RFC 8414 / OIDC).
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

8 checks to fix

  1. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks ChatGPT.

    Measured Not found: https://api.meacheal.ai/.well-known/oauth-protected-resource/mcp -> 404; https://api.meacheal.ai/.well-known/oauth-protected-resource -> 404

    Serve RFC 9728 metadata at /.well-known/oauth-protected-resource (plus the path-suffixed form) with "resource" and "authorization_servers".

  2. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks ChatGPT and Gemini.

    Measured Not found: https://api.meacheal.ai/.well-known/oauth-authorization-server -> 404; https://api.meacheal.ai/.well-known/openid-configuration -> 404

    Serve RFC 8414 metadata at <issuer>/.well-known/oauth-authorization-server with authorization_endpoint, token_endpoint and response_types_supported ["code"].

  3. Fails

    Sign-in method the store supports (OAuth or none)

    auth_method

    Blocks ChatGPT and Gemini.

    Measured unknown method: HTTP 401 and no working OAuth discovery: the server asks for a Bearer token but its OAuth metadata could not be found

    ChatGPT and Gemini cannot send a static API key or token: add MCP OAuth (protected resource metadata and authorization server metadata), or serve the tools without auth. Claude accepts a static credential in a request header only in a beta

  4. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  5. Warning

    401 carries WWW-Authenticate resource_metadata

    auth_challenge

    Measured unknown method: WWW-Authenticate bearer without resource_metadata

    Add resource_metadata="https://<host>/.well-known/oauth-protected-resource<path>" to the WWW-Authenticate: Bearer header on 401.

  6. Warning

    Tool descriptions

    tool_descriptions

    Measured 14 over 2000 chars: search_suppliers, get_supplier_detail, search_fabrics, get_fabric_detail, search_clusters and 9 more

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  7. Warning

    initialize latency

    latency

    Measured 3474 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  8. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

13 checks passed, 6 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool.

Not run. Resource metadata "resource" equals the server URL, First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for MRC Data

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.meacheal.ai%2Fmcp)](https://www.mcpstamp.com/r/ai-meacheal-mrc-data/)

HTML

<a href="https://www.mcpstamp.com/r/ai-meacheal-mrc-data/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.meacheal.ai%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

China's apparel supply chain data for AI: 1,000+ suppliers, 350+ fabrics, 170+ clusters.
Registry name
ai.meacheal/mrc-data
Remote URL
https://api.meacheal.ai/mcp
Version
2.2.2
Website
api.meacheal.ai
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026