Maatsii

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

사용해야 할까요

품질 및 안전성

B
설명 품질
100%
스키마 완전성
70%
이름 품질
80%
오염 위험
60%
권한 일치
100%
프로토콜 준수
100%

발견 사항 (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains suspicious base64-like encoded stringmaatsii_list_setups에서
  • MEDIUMTool description contains suspicious base64-like encoded stringmaatsii_get_setup에서

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~3,059토큰 (도구 정의)
~1.7 KB일반적인 응답 크기
상당한 주의 영향 (128k 컨텍스트의 2.39%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

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

원격 엔드포인트

https://mcp.maatsii.com/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (10)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢maatsii_get_chart(id_or_ticker, cb, image_mode, include_images)

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).

입력 스키마

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

출력 스키마

{
  "type": "object",
  "properties": {
    "charts": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "symbol": {
            "type": "string"
          },
          "interval": {
            "type": "string"
          },
          "group": {
            "type": "string"
          },
          "url": {
            "type": "string"
          },
          "image": {
            "type": "string",
            "enum": [
              "inline",
              "url_only",
              "failed"
            ]
          },
          "bytes": {
            "type": "integer"
          },
          "sha256": {
            "type": "string"
          },
          "fetched_at": {
            "type": "string"
          },
          "frame_ts": {
            "type": "string"
          }
        },
        "required": [
          "id",
          "symbol",
          "interval",
          "group",
          "url",
          "image"
        ],
        "additionalProperties": false
      }
    },
    "omitted": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "reason": {
            "type": "string"
          }
        },
        "required": [
          "id",
          "reason"
        ],
        "additionalProperties": false
      }
    },
    "degraded": {
      "type": "boolean"
    }
  },
  "required": [
    "charts",
    "omitted",
    "degraded"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢maatsii_get_group(group, ids, max_images, image_mode, include_images)

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "group": {
      "type": "string",
      "description": "Group name or alias, e.g. NQ, BTC, GOLD, VIX, PLTR, CREDIT"
    },
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only these chart ids from the group, e.g. [\"c1\",\"c4\"]"
    },
    "max_images": {
      "type": "integer",
      "minimum": 1,
      "description": "OPTIONAL caller hint: inline at most this many JPEGs (the rest stay url-only). Omitted = EVERY requested chart inline — there is no server maximum."
    },
    "image_mode": {
      "type": "string",
      "enum": [
        "inline",
        "url_only",
        "both"
      ],
      "description": "\"both\" (default) = JPEG inline + url in text; \"inline\" = same; \"url_only\" = no image bytes, url only"
    },
    "include_images": {
      "type": "boolean",
      "description": "Default true. false is equivalent to image_mode url_only."
    }
  },
  "required": [
    "group"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

출력 스키마

{
  "type": "object",
  "properties": {
    "charts": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "symbol": {
            "type": "string"
          },
          "interval": {
            "type": "string"
          },
          "group": {
            "type": "string"
          },
          "url": {
            "type": "string"
          },
          "image": {
            "type": "string",
            "enum": [
              "inline",
              "url_only",
              "failed"
            ]
          },
          "bytes": {
            "type": "integer"
          },
          "sha256": {
            "type": "string"
          },
          "fetched_at": {
            "type": "string"
          },
          "frame_ts": {
            "type": "string"
          }
        },
        "required": [
          "id",
          "symbol",
          "interval",
          "group",
          "url",
          "image"
        ],
        "additionalProperties": false
      }
    },
    "omitted": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "reason": {
            "type": "string"
          }
        },
        "required": [
          "id",
          "reason"
        ],
        "additionalProperties": false
      }
    },
    "degraded": {
      "type": "boolean"
    }
  },
  "required": [
    "charts",
    "omitted",
    "degraded"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢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.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢maatsii_list_setups(type, direction, timeframe, category, detail)

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.

입력 스키마

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

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "vision_features": {
      "type": "object",
      "properties": {
        "dominant_bias": {
          "type": "string"
        },
        "raw_vision_text": {
          "type": "string"
        },
        "conditions": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": true,
      "description": "Boolean structure flags (fan_support_test, pullback_to_fan, tick_absorption, ...), dominant_bias, raw_vision_text, optional conditions[] — see the vision_features concept"
    },
    "timeframes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Intervals of the charts the features were read from, e.g. [\"100T\",\"15M\",\"1H\"]. Required for TICK setup eligibility."
    },
    "groups_read": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Group aliases the client fetched this turn (e.g. [\"NQ\",\"VIX\"]); used only to allow the vol-gated setup #78."
    },
    "max_results": {
      "type": "integer",
      "minimum": 1,
      "description": "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)."
    }
  },
  "required": [
    "vision_features"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢maatsii_get_setup(id)

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.

입력 스키마

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

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢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 — to produce a full TA with actionable levels.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢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.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢maatsii_get_concept(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.

입력 스키마

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

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 10개
검증됨버전이 기록되지 않음도구 10개