bots.st/maatsii
Maatsii
Fetch LinReg fan charts and playbooks
2609 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 10
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.maatsii.com/mcp
What it can do
| Tool | What it says it does |
|---|---|
maatsii_analysis_framework | 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 —… |
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… |
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. |
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… |
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… |
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… |
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… |
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… |
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)… |
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'… |
In its maker's words
Live LinReg fan charts, 64-setup playbook, 11-section MTF TA. Remote MCP, no API key.
- Website
- maatsii.com
- Source
- github.com/BL3IP/maatsii-cursor-plugin
- Publisher
- maatsii.com
- Listed from
- the official MCP Registry as
com.maatsii/linreg - Version
- 1.5.2, updated 22 Sep 2026
- Kinds of work
- Images, video and audio, AI models and agent tools, Browser and automation
The domain it lives on
- maatsii.com
- registered 15 Aug 2025 (1 year ago), at NameCheap, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2609 ms | |
| Answered | 2321 ms | |
| Answered | 647 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.