LABSCO SUMMARY

Bring your own market data source — the API base URL is a blank you fill in.

The server does the analysis; where the trades come from is your decision, set by the base URL. That makes it adaptable to whichever data provider you already pay for, and it also means there is nothing to try until you have one. The fetch window is explicit — how many trades and how many days — so the cost of a run is something you set rather than discover.

What it is

A Node server for stock trading volume analysis. It reads trade data from a market API, identifies the price levels where volume concentrates — the volume walls — and persists what it finds in MongoDB so analysis carries across sessions.

What you get

Real-time trading volume analysis for a symbol
Detection of significant price levels where volume concentrates
Trading imbalance tracking, so you see which side is pressing
After-hours trading analysis
MongoDB-backed persistence rather than results that vanish with the session

Requirements

A running MongoDB instance, access to a stock market API, and Node.js v20 or higher. Run it with npx -y volume-wall-detector-mcp@latest. Configuration is entirely environment variables: API_BASE_URL for the market data source; MONGO_HOST, MONGO_PORT, MONGO_DATABASE, MONGO_USER, MONGO_PASSWORD, MONGO_AUTH_SOURCE and MONGO_AUTH_MECHANISM for storage; TIMEZONE, PAGE_SIZE, TRADES_TO_FETCH and DAYS_TO_FETCH for how much data to pull; TRANSPORT_TYPE and PORT for transport. The npm package is volume-wall-detector-mcp, version 1.0.1.

Setup effort

One command plus credentials — npx -y volume-wall-detector-mcp@latest, then supply credentials

See installation options

USE CASES

01

Finding where the volume actually sits

Detect the price levels where trading concentrates instead of eyeballing a chart.

02

Reading which way pressure is leaning

Track the buy and sell imbalance around those levels.

03

Looking at what happened after the close

Analyse after-hours activity alongside the regular session.

04

Keeping the analysis across sessions

Persist results to your own MongoDB rather than recomputing every time.

BEFORE YOU INSTALL

What to know first

Requires

npx on PATH
Node.js
MONGO_PASSWORD in your environment
API_BASE_URL in your environment

Where it runs

Both documented clients run the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y volume-wall-detector-mcp@latest

MCP Clients

Cline

CLINE · JSON

{
  "mcpServers": {
    "volume-wall-detector-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "volume-wall-detector-mcp@latest"
      ],
      "env": {
        "TIMEZONE": "GMT+7",
        "API_BASE_URL": "<YOUR_API_BASE_URL>",
        "MONGO_HOST": "localhost",
        "MONGO_PORT": "27017",
        "MONGO_DATABASE": "volume_wall_detector",
        "MONGO_USER": "admin",
        "MONGO_PASSWORD": "password",
        "MONGO_AUTH_SOURCE": "admin",
        "MONGO_AUTH_MECHANISM": "SCRAM-SHA-1",
        "PAGE_SIZE": "50",
        "TRADES_TO_FETCH": "10000",
        "DAYS_TO_FETCH": "1",
        "TRANSPORT_TYPE": "stdio",
        "PORT": "8080"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "volume-wall-detector-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "volume-wall-detector-mcp@latest"
      ],
      "env": {
        "TIMEZONE": "GMT+7",
        "API_BASE_URL": "<YOUR_API_BASE_URL>",
        "MONGO_HOST": "localhost",
        "MONGO_PORT": "27017",
        "MONGO_DATABASE": "volume_wall_detector",
        "MONGO_USER": "admin",
        "MONGO_PASSWORD": "password",
        "MONGO_AUTH_SOURCE": "admin",
        "MONGO_AUTH_MECHANISM": "SCRAM-SHA-1",
        "PAGE_SIZE": "50",
        "TRADES_TO_FETCH": "10000",
        "DAYS_TO_FETCH": "1",
        "TRANSPORT_TYPE": "stdio",
        "PORT": "8080"
      }
    }
  }
}

Volume Wall Detector