maatsii-linreg-connector

endpoint

https://mcp.maatsii.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is maatsii-linreg-connector live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is maatsii-linreg-connector free to use?

Yes — the hub reached it with no key and no payment.

What tools does maatsii-linreg-connector have?

10 tools: maatsii_get_chart, maatsii_get_concept, maatsii_list_setups, maatsii_match_setup, maatsii_get_setup, maatsii_get_group, maatsii_analysis_framework, maatsii_reading_guide, ….

Is maatsii-linreg-connector safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• maatsii_analysis_framework reads open 1h ago

  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.

  mcp-tool

  12345

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

  arguments 5 lines copy
• maatsii_reading_guide reads open 22h ago

  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.

  mcp-tool

  12345

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

  arguments 5 lines copy
• maatsii_chart_map reads open 1h ago

  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.

  mcp-tool

  12345

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

  arguments 5 lines copy
• maatsii_fan_guide reads open 1h ago

  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.

  mcp-tool

  12345

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

  arguments 5 lines copy
• maatsii_get_chart reads unknown 22h ago

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

  mcp-tool

  12345678910111213141516171819202122232425262728293031

  {
    "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
  }

  arguments 31 lines copy
• maatsii_get_concept reads unknown 22h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "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
  }

  arguments 14 lines copy
• maatsii_list_setups reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839

  {
    "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
  }

  arguments 39 lines copy
• maatsii_match_setup reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "vision_features"
    ],
    "properties": {
      "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)."
      },
      "vision_features": {
        "type": "object",
        "properties": {
          "conditions": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "dominant_bias": {
            "type": "string"
          },
          "raw_vision_text": {
            "type": "string"
          }
        },
        "description": "Boolean structure flags (fan_support_test, pullback_to_fan, tick_absorption, ...), dominant_bias, raw_vision_text, optional conditions[] — see the vision_features concept",
        "additionalProperties": true
      }
    },
    "additionalProperties": false
  }

  arguments 48 lines copy
• maatsii_get_setup reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "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
  }

  arguments 17 lines copy
• maatsii_get_group reads unknown 13h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "group"
    ],
    "properties": {
      "ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Only these chart ids from the group, e.g. [\"c1\",\"c4\"]"
      },
      "group": {
        "type": "string",
        "description": "Group name or alias, e.g. NQ, BTC, GOLD, VIX, PLTR, CREDIT"
      },
      "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"
      },
      "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."
      },
      "include_images": {
        "type": "boolean",
        "description": "Default true. false is equivalent to image_mode url_only."
      }
    },
    "additionalProperties": false
  }

  arguments 39 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.