Reins

io.github.R2RlabsPublished by GitHub account R2Rlabsv0.1.5Updated Oct 24, 2026

Risk limits and an audit log for AI agents trading Hyperliquid, enforced outside the model.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that lets an AI agent trade Hyperliquid under enforced risk limits, with paper or live mode and a decision log.

What you can do
  • Trade Hyperliquid markets in paper mode (live prices, simulated fills) or live mode, restricted to the configured symbols.
  • Apply risk limits outside the model: maximum leverage, maximum position size per market, and a daily realised-loss cutoff that refuses new risk.
  • Optionally refuse any order that adds risk without a stop-loss.
  • Record each action as a JSON line with the agent's stated reason to a decision log file.
  • Persist a paper account between runs in a file.
When to use it
Use it when you want an AI agent to place or simulate Hyperliquid trades but need hard limits, symbol allowlists and an audit trail that the model cannot override. Paper mode is the sensible starting point before any live trading.
Requirements
Runs locally via npx from the npm package, so Node.js is needed. Required settings: REINS_SYMBOLS, REINS_MAX_POSITION_USD and REINS_DAILY_LOSS_USD. Live mode additionally needs REINS_ACCOUNT_ADDRESS, REINS_PRIVATE_KEY (an API wallet key) and a one-time builder-fee approval from the account. Optional: REINS_MODE, REINS_NETWORK, REINS_MAX_LEVERAGE, REINS_REQUIRE_STOP_LOSS, REINS_LOG_FILE, REINS_PAPER_FILE. Network access to Hyperliquid.
Before you install
Live mode spends real money and mainnet is the real network. REINS_PRIVATE_KEY is a trading credential: use an API wallet key that can trade but not withdraw, never the account's own key. Live trading requires approving a 2 bp builder fee from the account. Orders and risk decisions are written to the log file, which may contain the agent's stated reasons.

Installation

In SourceWeft

  1. Open Reins in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.5LatestSep 24, 2026
  2. v0.1.4Sep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.