Skip to main content
Glama
Sentinel-MCP

Sentinel-MCP

by AnahadhBirdh

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:

  • core creates the MCP server and cross-cutting concerns such as logging and errors.

  • config validates the runtime environment before startup.

  • tools contains independently registerable MCP capabilities.

  • services contains application logic that tools depend on.

  • models contains 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 .env

Development

pnpm dev

Build and run

pnpm build
pnpm start

The 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:check

Folder 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

SENTINEL_APP_NAME

Sentinel-MCP

Server identity exposed to clients

SENTINEL_APP_VERSION

0.1.0-alpha

Server version exposed to clients

SENTINEL_LOG_LEVEL

info

Pino log level

SENTINEL_TRANSPORT

stdio

MCP transport for this milestone

Roadmap

  1. Provider interfaces and resilient market-data adapters.

  2. Shared cache, rate-limit, and retry policies.

  3. Symbol lookup and market intelligence tools.

  4. News enrichment and configurable alerting.

  5. Optional authenticated provider integrations.

License

Choose and add an open-source license before public distribution.

Available Tools

1 tool
get_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

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of ambiguity. The tool's purpose is clearly distinct by default.

    Naming Consistency5/5

    With a single tool named 'get_server_info', naming is trivially consistent. The pattern follows a clear verb_noun structure.

    Tool Count2/5

    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.

    Completeness1/5

    The tool surface is severely incomplete for any meaningful server interaction. There are no CRUD or lifecycle operations, merely a single informational endpoint.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for Interactive Brokers that exposes market data, positions, and account info as MCP tools.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      General-purpose MCP server with built-in tools for HTTP, JSON, and datetime operations, supporting pluggable modules and security defaults.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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
    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      15
      MIT