Mudrex MCP Server

io.github.mudrexPublished by GitHub account mudrexv1.0.0Updated Oct 24, 2026

MCP server for Mudrex futures trading enabling AI agents to securely access data and risk tools.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote Mudrex MCP server that lets an AI assistant access Mudrex futures trading data and risk tools through an API key.

What you can do
  • Access Mudrex futures trading data and risk tools from an AI assistant.
  • No individual tools are listed in the manifest, so the exact operations are not documented here; the server is described as giving agents secure access to trading data and risk tools.
When to use it
Use it when you want an assistant to work with Mudrex futures trading information and risk-related tooling, for example to review positions or risk within a Mudrex account.
Requirements
A remote MCP endpoint at mudrex.com using streamable HTTP; no local package or runtime is needed. A Mudrex API secret key is required and passed in the X-Authentication header.
Before you install
The server requires a Mudrex API secret key in the X-Authentication header, which grants access to a trading account; treat it as sensitive and scope or revoke it as needed. It concerns futures trading, so tools may expose account or position data and could involve orders or funds; confirm what each tool does before letting an assistant act.

Installation

In SourceWeft

  1. Open Mudrex MCP Server in the dashboard and add it to a workspace.
  2. Connect X-Authentication credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mudrex%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mudrex": {
      "type": "http",
      "url": "https://mudrex.com/mcp",
      "headers": {
        "X-Authentication": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.