Sentinel-MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sentinel-MCP show server diagnostics"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sentinel-MCP
Sentinel-MCP is an extensible trading-intelligence platform whose first interface is a Model Context Protocol (MCP) server. Milestone 1 provides a robust server foundation: configuration, structured logging, automatic tool registration, error boundaries, testing, and a diagnostic tool.
Trading execution and market-data integrations are intentionally out of scope for this milestone.
Architecture
The application follows dependency-oriented boundaries:
corecreates the MCP server and cross-cutting concerns such as logging and errors.configvalidates the runtime environment before startup.toolscontains independently registerable MCP capabilities.servicescontains application logic that tools depend on.modelscontains stable, provider-agnostic data contracts.
Future provider adapters (TradingView, Dhan, NSE, news, and caching) can be added behind service interfaces without changing the MCP entry point.
Related MCP server: @zuupee/mcp-server
Requirements
Node.js 22 or later (current LTS recommended)
pnpm 9 or later
Installation
git clone <your-repository-url>
cd sentinel-mcp
pnpm install
cp .env.example .envDevelopment
pnpm devBuild and run
pnpm build
pnpm startThe server communicates over standard input/output, as required by local MCP clients. Logs are written to stderr so they never corrupt the MCP protocol stream.
To use it with Claude Desktop after building, add a server entry that invokes the built file:
{
"mcpServers": {
"sentinel-mcp": {
"command": "node",
"args": ["/absolute/path/to/sentinel-mcp/dist/index.js"]
}
}
}Available tools
get_server_info
Returns structured runtime data including server name, version, status, ISO timestamp, uptime, Node.js version, and host platform. It is a safe connection and health diagnostic.
Quality commands
pnpm typecheck
pnpm lint
pnpm test
pnpm format:checkFolder structure
src/
config/ Environment validation and runtime settings
core/ Server composition, errors, logging
models/ Provider-agnostic application contracts
providers/ External-provider contracts and future adapters
schemas/ Shared validation schemas
services/ Reusable application services
tools/ Self-registering MCP tools and registry
cache/ Cache implementations and policies
types/ Shared TypeScript declarations
utils/ Small, framework-independent helpers
tests/ Vitest coverage for foundation components
docs/ Project documentation (reserved for design documents)
scripts/ Project automation (reserved for operational scripts)Configuration
Copy .env.example to .env. The defaults work for local development.
Variable | Default | Purpose |
|
| Server identity exposed to clients |
|
| Server version exposed to clients |
|
| Pino log level |
|
| MCP transport for this milestone |
Roadmap
Provider interfaces and resilient market-data adapters.
Shared cache, rate-limit, and retry policies.
Symbol lookup and market intelligence tools.
News enrichment and configurable alerting.
Optional authenticated provider integrations.
License
Choose and add an open-source license before public distribution.
Available Tools
1 toolget_server_infoGet server informationA
Returns the Sentinel-MCP version and current runtime status.
Inputs: no named parameters. Returns: name, status, uptime, version, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity. The tool's purpose is clearly distinct by default.
With a single tool named 'get_server_info', naming is trivially consistent. The pattern follows a clear verb_noun structure.
A single tool that only returns server info is extremely limited. While it may serve a niche purpose, it feels insufficiently scoped for a typical MCP server, bordering on trivial.
The tool surface is severely incomplete for any meaningful server interaction. There are no CRUD or lifecycle operations, merely a single informational endpoint.
Maintenance
Related MCP Connectors
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents
JW3.ai remote MCP server for market reads and confirm-gated trading execution.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceRead-only MCP server for Interactive Brokers that exposes market data, positions, and account info as MCP tools.8MIT
- AlicenseNot gradedqualityDmaintenanceGeneral-purpose MCP server with built-in tools for HTTP, JSON, and datetime operations, supporting pluggable modules and security defaults.MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that bridges AI coding agents with MetaTrader 5 for inspection, market data, MQL5 development, compiling, Strategy Tester review, workspace sync, logs, audit trails, demo trading, and carefully gated live trading.MIT
- AlicenseBqualityDmaintenanceA read-only-by-default MCP server for Interactive Brokers that exposes account, positions, PnL, market data, and trade history from a local TWS/IB Gateway session, with optional trading capabilities.15MIT