Maatsii

Working · 1.9 s

com.maatsii/linregv1.5.2 Domain verified

Live LinReg fan charts, 64-setup playbook, 11-section MTF TA. Remote MCP, no API key.

Finance & Payments

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://mcp.maatsii.com/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

maatsii_analysis_framework Read-only

The 11-section multi-timeframe (MTF) LinReg analysis structure — the per-group timeframe hierarchy (use the intervals you actually fetched), alignment/divergence scoring, setup verification via playbook text, optional intermarket section, and the Master Trade List + bull/base/bear scenario tree — to produce a full TA with actionable levels.

This tool takes no arguments.

Tools (10)

maatsii_analysis_framework

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

maatsii_chart_map

The authoritative 200-chart / 25-group map (id -> symbol/timeframe/group), including the group ALIASES (NQ, GOLD, PLTR, ...) and the derived tickCharts inventory (which ids are 100T/1000T tick charts). Chart ids are non-contiguous; use this to route a symbol to the right ids. The printed header on a render always wins over the map.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

maatsii_fan_guide

LinReg fan geometry: what the fans are (EQ centerline + S1-3/R1-3 rails at ±1/2/3σ), rail parity (R≈S), EQ mean-reversion, the <TF> <R|S|EQ> label convention, confluence zones (3+ multi-timeframe lines converging), and slope alignment — how to read fan structure like the methodology intends.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

maatsii_get_chart

Get ONE fresh Maatsii chart by id (c1..c200) or ticker (NQ_100T, BTCUSD, PLTR). Returns the chart JPEG INLINE (type=image) plus a JSON metadata block with the render-ready api.maatsii.com url (unique cachebuster), symbol, timeframe and group. Vision the image; the printed chart title is ground truth for symbol+timeframe; prices are read off the RIGHT AXIS (maatsii_reading_guide).

read-only

Argument	Type	Description
cb	string	Optional cachebuster [A-Za-z0-9._-]{1,64}; a fresh one is generated if omitted or invalid
image_mode	string	"both" (default) = JPEG inline + url in text; "inline" = same; "url_only" = no image bytes, url only
id_or_ticker*	string	Canonical id c1..c200, or a ticker like NQ_100T / BTCUSD / PLTR
include_images	boolean	Default true. false is equivalent to image_mode url_only.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id_or_ticker"
  ],
  "properties": {
    "cb": {
      "type": "string",
      "description": "Optional cachebuster [A-Za-z0-9._-]{1,64}; a fresh one is generated if omitted or invalid"
    },
    "image_mode": {
      "enum": [
        "inline",
        "url_only",
        "both"
      ],
      "type": "string",
      "description": "\"both\" (default) = JPEG inline + url in text; \"inline\" = same; \"url_only\" = no image bytes, url only"
    },
    "id_or_ticker": {
      "type": "string",
      "description": "Canonical id c1..c200, or a ticker like NQ_100T / BTCUSD / PLTR"
    },
    "include_images": {
      "type": "boolean",
      "description": "Default true. false is equivalent to image_mode url_only."
    }
  },
  "additionalProperties": false
}

maatsii_get_concept

Explain a Maatsii concept in a few sentences: rail parity, fan confluence, EQ centerline, strength tiers, catalog direction, playbook fields, setup hint only, vision features, VRVP not VWAP, MTF alignment, invalidation logic, tick structure, chart freshness, fetch gate. Unknown concepts return the list of known ones.

read-only

Argument	Type	Description
concept*	string	Concept name, e.g. 'playbook fields' or 'catalog direction'

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "concept"
  ],
  "properties": {
    "concept": {
      "type": "string",
      "description": "Concept name, e.g. 'playbook fields' or 'catalog direction'"
    }
  },
  "additionalProperties": false
}

maatsii_get_group

Get FRESH charts for every chart in a group (the REAL non-contiguous ids) — each chart's JPEG INLINE (type=image) plus one JSON metadata block listing every id with its api.maatsii.com url, symbol, interval. Accepts a friendly name/alias (NQ, ES, YM, RTY, BTC, ETH, GOLD, ENERGY, DXY, VIX, PLTR, NVDA, HYG, MACRO, CREDIT, ...). Rates note: YIELDS/ZN/RATES = the 10-Year group only; the curve/credit complex is CREDIT. EVERY chart in the group is inlined by default — there is no server image cap; use ids:[...] (or the optional max_images hint) to take a subset, image_mode:"url_only" to skip bytes. The metadata always lists the whole group. Vision EVERY chart; the MTF hierarchy for your analysis is the intervals these charts actually have.

read-only

Argument	Type	Description
ids	array	Only these chart ids from the group, e.g. ["c1","c4"]
group*	string	Group name or alias, e.g. NQ, BTC, GOLD, VIX, PLTR, CREDIT
image_mode	string	"both" (default) = JPEG inline + url in text; "inline" = same; "url_only" = no image bytes, url only
max_images	integer	OPTIONAL caller hint: inline at most this many JPEGs (the rest stay url-only). Omitted = EVERY requested chart inline — there is no server maximum.
include_images	boolean	Default true. false is equivalent to image_mode url_only.

Input schema (JSON)

maatsii_get_setup

Get the full public playbook for ONE active setup by id (accepts "#19", "19", "T1", "t1"). Returns the catalog card (id/name/category/direction/description/strengthTier/appliesTo) plus logic/entry/confirmation/exit/stop/target/edge text. Use it to verify a candidate against the chart before citing it. There are 64 active setups (45 Fan + 19 Tick); ids outside the active library return an error. Catalog direction is not the trade side.

read-only

Argument	Type	Description
id*	string \| number	Setup id, e.g. "#19", 19, or "T1"

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": [
        "string",
        "number"
      ],
      "description": "Setup id, e.g. \"#19\", 19, or \"T1\""
    }
  },
  "additionalProperties": false
}

maatsii_list_setups

List all 64 active LinReg setups (45 Fan #-series + 19 Tick T-series). detail:"full" (default) includes each setup's playbook text (logic/entry/confirmation/exit/stop/target/edge); detail:"card" is a lightweight catalog for browsing. Filter by type (FAN|TICK|ALL), direction, category, and/or timeframe (TICK setups — and the tick-native Fan #34 — apply ONLY on 100T/1000T tick charts, never on time-based intervals). Note: catalog direction is the pattern's native side, NOT the trade side, and strengthTier is an ID-band label, not live chart state.

read-only

Argument	Type	Description
type	string
detail	string	"card" = catalog fields only; "full" (default) adds the playbook text
category	string	Filter by category slug, e.g. advanced_pattern, confluence, correlation_intermarket, divergence, ...
direction	string
timeframe	string	Filter to setups applicable on this interval, e.g. 1H or 100T

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "type": {
      "enum": [
        "FAN",
        "TICK",
        "ALL"
      ],
      "type": "string"
    },
    "detail": {
      "enum": [
        "card",
        "full"
      ],
      "type": "string",
      "description": "\"card\" = catalog fields only; \"full\" (default) adds the playbook text"
    },
    "category": {
      "type": "string",
      "description": "Filter by category slug, e.g. advanced_pattern, confluence, correlation_intermarket, divergence, ..."
    },
    "direction": {
      "enum": [
        "LONG",
        "SHORT",
        "ANY"
      ],
      "type": "string"
    },
    "timeframe": {
      "type": "string",
      "description": "Filter to setups applicable on this interval, e.g. 1H or 100T"
    }
  },
  "additionalProperties": false
}

maatsii_match_setup

OPTIONAL hint — do not lead a TA with it. THE CLIENT matches setups by visioning the fetched chart JPEGs and verifying candidates via maatsii_get_setup; this tool only cross-checks vision_features (boolean flags, plus raw_vision_text scanned for natural TA language with negations respected) against the 64-setup active library and may return best null (correct on empty/thin input — never invents a setup). Results carry a QUALITATIVE fit label + playbook text; ignore the catalog direction label (trade side = highest fetched TF EQ slope). Pass timeframes — the chart intervals you actually read; TICK setups (T-series) and the tick-native Fan #34 are only eligible when a 100T/1000T tick chart is in scope. Pass groups_read — the group aliases you fetched this turn; cross-asset setup #78 is only eligible when a vol group (VIX/MOVE) was fetched.

read-only

Argument	Type	Description
timeframes	array	Intervals of the charts the features were read from, e.g. ["100T","15M","1H"]. Required for TICK setup eligibility.
groups_read	array	Group aliases the client fetched this turn (e.g. ["NQ","VIX"]); used only to allow the vol-gated setup #78.
max_results	integer	Optional; the default of 4 is a hint-quality default, NOT a cap — any positive integer is accepted (bounded only by the active library size).
vision_features*	object	Boolean structure flags (fan_support_test, pullback_to_fan, tick_absorption, ...), dominant_bias, raw_vision_text, optional conditions[] — see the vision_features concept

maatsii_reading_guide

How to read a Maatsii chart correctly: the price is on the RIGHT AXIS; the black last-price tag = header Close; fan labels are <TF> <type> (R/S/EQ); no VRVP/volume-profile or VWAP is printed on the template (header Vol = bar volume; mid = labelled EQ). No OCR, no pixel math, no 'black box' hunting.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}