Sentinel Execution Mcp

io.github.rohith1125Published by GitHub account rohith1125v0.1.2Updated Oct 24, 2026

AI-controlled algorithmic trading engine exposing 40 MCP tools across 9 namespaces.

The publisher's own server: Execution Market

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

A local MCP server that lets an assistant drive Sentinel, an algorithmic trading engine, for watchlists, market data, risk checks, paper orders and audit review

What you can do
Manage watchlists: add, remove, list and group symbols, and edit notes or group assignments for them. Read market data: snapshots, OHLCV bars, bid/ask quotes and provider health. Classify market regimes and review regime history. Scan strategies for signals, evaluate a single symbol and list registered strategies. Run risk checks, read exposure and drawdown, and enable or disable kill switches. Submit and cancel paper orders, list and inspect orders, and reconcile engine state with the broker. Review portfolio status, positions and closed history, govern strategy lifecycle, and query or export audit records.
When to use it
Useful for paper-trading research and experimentation where an assistant should inspect market data, test strategies and place simulated orders under risk limits. Not intended for unsupervised live trading.
Requirements
Runs locally as a Node.js 20+ process (npm package) that calls a Sentinel engine over HTTP at ENGINE_BASE_URL (default localhost:8100). The engine needs Python 3.12, PostgreSQL 15+ and Redis 7+, or Docker. Market data defaults to a mock provider; real data needs ALPACA_API_KEY and ALPACA_API_SECRET. Engine auth uses SENTINEL_MASTER_KEY and SENTINEL_API_KEYS_JSON.
Before you install
Setting APP_ENV=live with real Alpaca credentials places real orders with real money; the README says the software is for paper trading and research only. Tools write and change state: orders are submitted and cancelled, kill switches toggled, strategies promoted or suspended, and watchlists edited. Engine auth is on by default and can be disabled for local development only. Risk limits are defaults that should be checked against your own tolerance.

Installation

In SourceWeft

  1. Open Sentinel Execution Mcp 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.

Other MCP clients

Follow the launch instructions in the repository.

README

Sentinel Execution MCP

[CI] [License: MIT]

A production-grade algorithmic trading control plane exposed as an MCP server — so Claude can manage watchlists, classify market regimes, validate risk, and submit paper orders through natural language.


What It Is

Sentinel is a two-package monorepo:

PackageLanguageRole
packages/enginePython 3.12 / FastAPIAll trading logic: risk checks, regime classification, order lifecycle, audit journal, strategy governance
packages/mcpTypeScript / Node 20Thin MCP server that routes 40+ tools to the engine via HTTP. Zero trading logic lives here.

Claude (or any MCP-compatible agent) talks to the MCP server. The MCP server talks to the engine. The engine owns the database and cache.


Architecture

  Claude Desktop (or any MCP agent)           │           │  MCP protocol (stdio or SSE)           ▼  ┌─────────────────────────┐  │   MCP Server            │  TypeScript · Zod validation · tool routing  │   (packages/mcp)        │  └────────────┬────────────┘               │  HTTP REST (localhost:8100)               ▼  ┌─────────────────────────┐  │   Engine API            │  Python · FastAPI · all trading logic  │   (packages/engine)     │  └──────────┬──────────────┘             │     ┌───────┴────────┐     ▼                ▼ PostgreSQL          Redis (orders,           (kill switch,  positions,         rate limits,  strategies,        cache)  audit log)

If the engine is unavailable, every MCP tool call returns an error immediately. There is no fallback or partial execution.


Quick Start (Docker — recommended)

The fastest way to get running. Requires Docker and Node.js 20+.

bash
# 1. Clone and configuregit clone https://github.com/rohith1125/sentinel-execution-mcp.gitcd sentinel-execution-mcpcp .env.example .env          # defaults work out of the box — no edits needed
# 2. Start Postgres + Redis + engine (runs migrations automatically)docker compose -f docker/docker-compose.yml up -d db redis engine
# Wait ~10 seconds, then verify the engine is healthy:curl http://localhost:8100/health# {"status": "ok", "provider": "mock", ...}
# 3. Build the MCP server (one-time)cd packages/mcpnpm installnpm run build

Then add Sentinel to Claude Desktop (see Connect Claude Desktop below) and restart Claude. That's it — all 40 tools are live.


Manual Setup (no Docker)

Use this if you have Postgres and Redis already running locally.

Prerequisites:

DependencyMinimum versionNotes
Python3.12Engine runtime — check with python3 --version
Node.js20MCP server runtime
PostgreSQL15+Primary data store
Redis7+Kill switch and cache

1. Clone and configure

bash
git clone https://github.com/rohith1125/sentinel-execution-mcp.gitcd sentinel-execution-mcpcp .env.example .env# Default values work for local paper-trading development — no edits required

2. Set up the engine

bash
cd packages/enginepython3.12 -m venv .venvsource .venv/bin/activate        # Windows: .venv\Scripts\activatepip install -e ".[dev]"

3. Run database migrations

bash
# From packages/engine with the venv activealembic upgrade head

4. Start the engine

bash
uvicorn sentinel.api:app --reload --port 8100

Verify it is running:

bash
curl http://localhost:8100/health# {"status": "ok", "env": "paper"}

5. Build and start the MCP server

Open a second terminal:

bash
cd packages/mcpnpm installnpm run buildnpm run dev     # stdio transport — for direct Claude Desktop integration

Connect Claude Desktop

Add the following to your Claude Desktop configuration file.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

Get the correct path by running this in your terminal:

bash
echo "$(pwd)/packages/mcp/dist/index.js"

Then paste it into the config:

json
{  "mcpServers": {    "sentinel": {      "command": "node",      "args": ["/absolute/path/to/sentinel-execution-mcp/packages/mcp/dist/index.js"],      "env": {        "ENGINE_BASE_URL": "http://localhost:8100",        "APP_ENV": "paper"      }    }  }}

Restart Claude Desktop after saving. You should see a hammer icon (🔨) in the chat input — click it to confirm Sentinel's 40 tools are loaded.


MCP Tools Reference

Sentinel exposes 40+ tools across nine categories. The MCP server name is sentinel.

CategoryToolDescription
Watchlistwatchlist.addAdd symbols to the trading watchlist, optionally assigned to a group
watchlist.removeRemove symbols; they will no longer appear in strategy scans
watchlist.listList active symbols, optionally filtered by group
watchlist.getGet details for a single symbol
watchlist.groupsList all named watchlist groups
watchlist.updateUpdate notes or group assignment for a symbol
Market Datamarket.snapshotLatest quote and trade data for one or more symbols
market.barsOHLCV bar history with configurable timeframe
market.quoteReal-time bid/ask spread for a symbol
market.healthCheck market data provider connectivity
Regimeregime.evaluateClassify current market regime using ATR, ADX, RSI, Bollinger Width, Hurst Exponent, VWAP, and Price Efficiency
regime.historyRetrieve historical regime snapshots for a symbol
Strategystrategy.scanScan the watchlist for signals across one or more strategies
strategy.signalEvaluate a single symbol against a specific strategy
strategy.listList all registered strategies and their current state
Risk / Kill Switchrisk.validate_tradeRun all 13+ risk checks against a proposed trade before submission
risk.kill_switch_statusGet the current state of all kill switches
risk.kill_switch_enableEnable a kill switch globally, per-strategy, or per-symbol
risk.kill_switch_disableDisable a kill switch (requires explicit reason)
risk.exposureCurrent gross and net exposure summary
risk.drawdownCurrent daily drawdown against configured limits
Portfolioportfolio.statusFull account overview: value, cash, equity, P&L, buying power
portfolio.positionsAll open positions with unrealized P&L
portfolio.historyClosed position history with realized P&L
Executionexecution.paper_orderSubmit a paper trading order (market, limit, stop, stop-limit)
execution.cancel_orderCancel a pending or partially filled order by ID
execution.get_orderGet the current state of a specific order
execution.list_ordersList orders filtered by status, symbol, or date range
execution.reconcileTrigger a manual reconciliation between engine state and broker
Governancegovernance.create_strategyRegister a new strategy in draft state
governance.promote_strategyAdvance a strategy: Draft → Research → Backtest → Paper → Live
governance.suspend_strategySuspend a live or paper strategy immediately
governance.list_strategiesList all strategies with their current lifecycle state
governance.evaluate_promotionCheck whether a strategy meets criteria for promotion
Auditaudit.explain_tradeFull human-readable explanation for a trade decision by audit event ID
audit.recent_eventsMost recent audit events, filterable by symbol or strategy
audit.trade_historyCompleted trade history with outcomes
audit.decision_logRaw decision log entries for a time window
audit.statsAggregate statistics: win rate, average P&L, Sharpe proxy
audit.exportExport audit records as CSV for a date range

Full tool documentation with parameter schemas: docs/mcp-tools.md


Environment Variables

Engine (packages/engine/.env)

VariableDefaultDescription
APP_ENVpaperdevelopment, paper, or live
DATABASE_URLpostgresql+asyncpg://sentinel:sentinel@localhost:5432/sentinelPostgreSQL connection string
REDIS_URLredis://localhost:6379/0Redis connection string
MARKET_DATA_PROVIDERmockmock (no credentials needed) or alpaca
ALPACA_API_KEY(empty)Required when MARKET_DATA_PROVIDER=alpaca
ALPACA_API_SECRET(empty)Required when MARKET_DATA_PROVIDER=alpaca
ALPACA_BASE_URLhttps://paper-api.alpaca.marketsUse https://api.alpaca.markets for live trading
MAX_POSITION_PCT0.05Maximum position size as a fraction of account equity (5%)
MAX_DAILY_DRAWDOWN_PCT0.02Hard daily loss limit (2%); trading halts if breached
MAX_GROSS_EXPOSURE_PCT0.80Maximum gross exposure across all positions (80%)
MAX_CONCURRENT_POSITIONS10Maximum number of simultaneously open positions
MAX_TRADE_RISK_PCT0.01Maximum risk per individual trade (1%)
PAPER_FILL_LATENCY_MS50Simulated fill latency in paper trading mode
SLIPPAGE_BPS5Simulated slippage in basis points
SENTINEL_AUTH_ENABLEDtrueSet to false for local development only
SENTINEL_MASTER_KEY(empty)Generate with python -m sentinel.auth.cli generate --name master --scopes admin
SENTINEL_API_KEYS_JSON(empty)JSON array of additional client key records

MCP Server (packages/mcp/.env)

VariableDefaultDescription
ENGINE_BASE_URLhttp://localhost:8100Base URL of the running engine service

See .env.example at the repo root for the complete annotated reference.


Example Workflow (Paper Trading)

# 1. Add symbolswatchlist.add(symbols=["NVDA", "MSFT", "AAPL"], group="tech")
# 2. Classify regimeregime.evaluate(symbol="NVDA", timeframe="1Day")
# 3. Scan for signalsstrategy.scan(group="tech", strategy="momentum_v1")
# 4. Validate before submittingrisk.validate_trade(symbol="NVDA", side="buy", qty=10, order_type="market")
# 5. Submit paper orderexecution.paper_order(symbol="NVDA", side="buy", qty=10, order_type="market")
# 6. Review portfolioportfolio.status()
# 7. Inspect the audit trailaudit.recent_events(symbol="NVDA", limit=1)audit.explain_trade(audit_event_id="evt-...")

Running Tests

Engine (Python)

bash
cd packages/enginesource .venv/bin/activatepytest tests/ -v

MCP Server (TypeScript)

bash
cd packages/mcppnpm test

Full CI (lint + type check + test)

bash
# From repo rootmake check

Repository Structure

sentinel-execution-mcp/├── packages/│   ├── engine/          # Python FastAPI trading engine│   │   ├── sentinel/    # Application source│   │   ├── tests/       # Pytest test suite│   │   └── alembic/     # Database migrations│   └── mcp/             # TypeScript MCP server│       └── src/│           └── tools/   # One file per tool category├── docker/              # Dockerfiles and docker-compose├── docs/                # Architecture, tool reference, risk model├── scripts/             # Setup and reset helpers└── .env.example         # Annotated environment variable reference

Safety Disclaimer

This software is for paper trading and research only unless you fully understand every component. Setting APP_ENV=live with real Alpaca credentials will place real orders with real money. The hard-coded risk limits are conservative defaults — verify they match your own risk tolerance before use. The authors accept no liability for financial losses.


License

MIT. See LICENSE.

Source: README.md at commit 2f8bc9f

Tools

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

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Execution integrations