Skip to content
Maatsii logo

Maatsii MCP server

Which MCP servers are Maatsii's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-23

← Back to Maatsii

Whose server it is
  • Registry namecom.maatsii/linregverified in the MCP registry

The registry name sits under maatsii.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-23
  • Stateanswerschecked 2026-10-23
  • Tools10
  • Server calls itselfmaatsii-linreg-connector
  • Server version1.5.1
  • Protocol version2025-06-18

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 256 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Read live futures charts inside Claude or ChatGPT; Give AI agents annotated chart frames through MCP.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "Read live futures charts inside Claude or ChatGPT", the likely first call is maatsii_get_chart.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer251 ms
  • Space in an agent's context≈ 2,322 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 98 of 100
  • Typed results2 of 10 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 10

What an agent can do with it

  • can do · Read live futures charts inside Claude or ChatGPT
  • not sure · Pull chart image URLs into trading scripts
  • can do · Give AI agents annotated chart frames through MCP

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-10-23
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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 =…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "linreg": {
      "type": "http",
      "url": "https://mcp.maatsii.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http maatsii https://mcp.maatsii.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.maatsii.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.