M
mishmar-io/mishmar
Mishmar is a risk management layer for trading bots
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · mishmar-io/mishmar · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
mishmar-io/mishmar;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# mishmar
Excerpted from the repository README (abridged)
Mishmar is a risk management layer for trading bots
and AI agents: every order is checked against your limits before it reaches
the exchange, large orders wait for your approval, and no key can trade
alone. This is the client side: the API contract, the test vectors every SDK
must pass, the agent's signer, the mishmar CLI and MCP server, and the
SDKs themselves. The engine that enforces the rules is a separate, private
repo; this one is what runs next to your agent.
Status: live. Mishmar runs with real money on Hyperliquid and Binance USDⓈ-M
futures, or on their testnets first. The contract, the Go packages, the
agent's signer and the mishmar CLI are here, and so are the Python and
TypeScript SDKs (mishmar on PyPI and npm). Binaries for Linux and macOS are
on the Releases page.
## Layout
spec/openapi.yaml the API contract, the single source of truth for every client and the engine
spec/vectors/ cross-language test vectors: proposal signing, agent request signing (agentAuth), the engine's signature on a decision,
an agent key's fingerprint, the trade sign-in's machine proof, the app setup text
api/ the contract as Go types (generated; make gen)
canon/ canonical JSON: the bytes an agent signs
agentkey/ the agent's Ed25519 identity key: parse the secret, sign, verify, sign requests
proposal/ build, validate and sign a proposal for POST /v1/proposals
decision/ verify the engine's signature on a decision, per signing version, from the decision as served
frost/ two-party FROST over Ed25519: the split key behind a Binance connectedAccount
ecdsa2p/ two-party ECDSA over secp256k1: the split key behind a Hyperliquid API wallet (keygen, presigning, signing)
signer/ the agent's signer: config, engine client, the checks, the signing rounds (FROST and two-party ECDSA), the poll loop;
signin/ (an AI app's trade sign-in) and daemon/ (the background signer behind mishmar mcp --app)
appsetup/ the setup text an AI app is given for trading through Mishmar from the person's computer
cmd/mishmar/ the CLI: keygen, add-agent, signer init|add-key|keygen|run|daemon, propose, read, mcp, daemon status|stop
mcp/ the MCP server behind mishmar mcp: the signer's tools for a language model, over stdio
python/ the Python SDK (mishmar on PyPI)
typescript/ the TypeScript SDK (mishmar on npm); no runtime dependencies
examples/ bots to copy from: two minimal ones (Python, TypeScript) and two rule walk-throughs (Hyperliquid testnet, Binance demo trading)
## Run the checks
Two-party ECDSA (ecdsa2p, Hyperliquid API wallets) is Coinbase's cb-mpc, C++
behind cgo, through the mishmar-io fork of cb-mpc-go
checked out next to this repo at the ref in cbmpc.ref (go.mod replaces
the module with ../cb-mpc-go). Its scripts/build_cpp.sh builds the
library once (CMake, a static OpenSSL 3.6.1 from its scripts/openssl), and
make runs every Go command through its scripts/go_with_cpp.sh, which sets
the cgo flags. Linux and macOS; Windows through WSL or Docker.
make test # Go packages, including the vectors and both signers
make lint
cd python && python -m pytest # the Python SDK against the same vectors
cd typescript && npm test # the TypeScript SDK against the same vectors (Node 22+)
and AI agents: every order is checked against your limits before it reaches
the exchange, large orders wait for your approval, and no key can trade
alone. This is the client side: the API contract, the test vectors every SDK
must pass, the agent's signer, the mishmar CLI and MCP server, and the
SDKs themselves. The engine that enforces the rules is a separate, private
repo; this one is what runs next to your agent.
Status: live. Mishmar runs with real money on Hyperliquid and Binance USDⓈ-M
futures, or on their testnets first. The contract, the Go packages, the
agent's signer and the mishmar CLI are here, and so are the Python and
TypeScript SDKs (mishmar on PyPI and npm). Binaries for Linux and macOS are
on the Releases page.
## Layout
spec/openapi.yaml the API contract, the single source of truth for every client and the engine
spec/vectors/ cross-language test vectors: proposal signing, agent request signing (agentAuth), the engine's signature on a decision,
an agent key's fingerprint, the trade sign-in's machine proof, the app setup text
api/ the contract as Go types (generated; make gen)
canon/ canonical JSON: the bytes an agent signs
agentkey/ the agent's Ed25519 identity key: parse the secret, sign, verify, sign requests
proposal/ build, validate and sign a proposal for POST /v1/proposals
decision/ verify the engine's signature on a decision, per signing version, from the decision as served
frost/ two-party FROST over Ed25519: the split key behind a Binance connectedAccount
ecdsa2p/ two-party ECDSA over secp256k1: the split key behind a Hyperliquid API wallet (keygen, presigning, signing)
signer/ the agent's signer: config, engine client, the checks, the signing rounds (FROST and two-party ECDSA), the poll loop;
signin/ (an AI app's trade sign-in) and daemon/ (the background signer behind mishmar mcp --app)
appsetup/ the setup text an AI app is given for trading through Mishmar from the person's computer
cmd/mishmar/ the CLI: keygen, add-agent, signer init|add-key|keygen|run|daemon, propose, read, mcp, daemon status|stop
mcp/ the MCP server behind mishmar mcp: the signer's tools for a language model, over stdio
python/ the Python SDK (mishmar on PyPI)
typescript/ the TypeScript SDK (mishmar on npm); no runtime dependencies
examples/ bots to copy from: two minimal ones (Python, TypeScript) and two rule walk-throughs (Hyperliquid testnet, Binance demo trading)
## Run the checks
Two-party ECDSA (ecdsa2p, Hyperliquid API wallets) is Coinbase's cb-mpc, C++
behind cgo, through the mishmar-io fork of cb-mpc-go
checked out next to this repo at the ref in cbmpc.ref (go.mod replaces
the module with ../cb-mpc-go). Its scripts/build_cpp.sh builds the
library once (CMake, a static OpenSSL 3.6.1 from its scripts/openssl), and
make runs every Go command through its scripts/go_with_cpp.sh, which sets
the cgo flags. Linux and macOS; Windows through WSL or Docker.
make test # Go packages, including the vectors and both signers
make lint
cd python && python -m pytest # the Python SDK against the same vectors
cd typescript && npm test # the TypeScript SDK against the same vectors (Node 22+)
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mishmar-io-mishmar/)
- Source
- awesome · https://github.com/mishmar-io/mishmar
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.