Skip to content
MCPSTAMP
MCP server report

Mixer4AI MCP server

com.mixer4ai/mixer4ai

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

Measured facts

Score
87B
Sign-in
OAuth
Tools listed
14
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by PKCE S256 advertised.
ChatGPT app directory Not ready Blocked by PKCE S256 advertised.
Gemini Connected Apps Not ready Blocked by First metadata URL Gemini tries answers 200 with the required fields and PKCE S256 advertised.
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

6 checks to fix

  1. Fails

    PKCE S256 advertised

    auth_pkce

    Blocks Claude, ChatGPT and Gemini.

    Measured code_challenge_methods_supported missing

    Support PKCE and advertise "code_challenge_methods_supported": ["S256"] (MCP clients refuse to proceed without it).

  2. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured Gemini tries https://login.microsoftonline.com/3283ffbc-6a9c-474a-8b2b-8fec24600f63/v2.0/.well-known/oauth-authorization-server first and gets HTTP 404; it uses

    Make https://login.microsoftonline.com/3283ffbc-6a9c-474a-8b2b-8fec24600f63/v2.0/.well-known/oauth-authorization-server answer HTTP 200 with the authorization server metadata (authorization_endpoint, token_endpoint, response_types_supported

  3. Fails

    GET answers SSE or 405

    get_stream

    Measured No response: timeout after 8000 ms

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

  4. Warning

    Client registration (DCR or Client ID Metadata Documents)

    auth_registration

    Measured No registration_endpoint and no client_id_metadata_document_supported

    Add a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.

  5. Warning

    initialize latency

    latency

    Measured 3444 ms

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

  6. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported missing

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

20 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), 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, Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata. 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 Mixer4AI

Markdown

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

HTML

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

About this server

Mixer4AI - verified AI agents, trusted introductions, for agents acting for real businesses.
Registry name
com.mixer4ai/mixer4ai
Remote URL
https://mcp.mixer4ai.com/
Version
1.0.0
Website
mixer4ai.com
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 B servers

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