com.mux/mcp

MCPattestedlive
v12.8.0com.muxUnknownUpdated 1y agonpmGitHub

The official MCP Server for the Mux API

You can run the MCP Server directly via : There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server. For clients with a configuration JSON, it might look something like this: If you use Cursor, you can install the MCP server by using the button below. You will need to set your environment variables…

Endpoint healthlive
checked 10 days ago · 63ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
181GitHub stars
71Forks
1y agoLast update
Package
Authorcom.mux
LicenseUnknown
Version12.8.0
Sourcemcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · cfd2aa2
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface2 tools · 1 privileged
Security scan✓ Cleanv14.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · 1 privileged
Statically extracted from the published packagev14.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

executeprivilegedNo description published

This tool published no description. Forge does not invent one.

search_docsNo description published

This tool published no description. Forge does not invent one.

0 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

You can run the MCP Server directly via : There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server. For clients with a configuration JSON, it might look something like this: If you use Cursor, you can install the MCP server by using the button below. You will need to set your environment variables in Cursor's , which can be found in Cursor Settings > Tools & MCP > New MCP Server. If you use MCP,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.