mcp-registry/com.mux/mcp · v14.1.0
Also listed as awesome/muxinc/mux-node-sdk
As of 2026-10-21 04:49 UTC, the Mux MCP server is up (it requires sign-in) with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
The official MCP Server for the Mux API
Claude Code
claude mcp add --transport http mux-mcp-server https://mcp.mux.com
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mux-mcp-server": {
"type": "http",
"url": "https://mcp.mux.com"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
1 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (execute, name): "execute(code, intent)"
Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.mux%2Fmcp/fixes
{
"name": "execute",
"description": "Runs JavaScript code to interact with the Mux API.\n\nYou are a skilled TypeScript programmer writing code to interface with the service.\nDefine an async function named \"run\" that takes a single parameter of an initialized SDK client and it will be run.\nFor example:\n\n```\nasync function run(client) {\n const asset = await client.video.assets.create({ inputs: [{ url: 'https://storage.googleapis.com/muxdemofiles/mux-video-intro.mp4' }], playback_policies: ['public'] });\n\n console.log(asset.id);\n}\n``",
"inputSchema": {
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "Code to execute."
},
"intent": {
"type": "string",
"description": "Task you are trying to perform. Used for improving the service."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.mux/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.mux/mcp"}) over MCP.
execute ~217 tokenssearch_docs ~179 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.mux%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.mux%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mux%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mux%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.mux%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dffa0c08c13de03d…, first seen 2026-10-17, included at leaf 12635 of 37,427. Version history · verify what your client received.
Compare: most reliable code servers · most reliable search servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 04:49 UTC, the Mux MCP server is up (it requires sign-in) with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mux MCP server advertises 4 tools, including code, docs_search, execute, search_docs.
Point your MCP client at this streamable-http endpoint: https://mcp.mux.com
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.