# Maatsii (remote · mcp.maatsii.com)

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

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.maatsii.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-maatsii-linreg/mcp.md), [page](https://verifymcp.io/servers/com-maatsii-linreg/mcp)

## Channel facts

- Endpoint: `https://mcp.maatsii.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 52/100
  - 20% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1835 tokens (~131/item across 14 items; 10 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (20% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Maatsii MCP server?

Maatsii is a hosted endpoint at https://mcp.maatsii.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-maatsii-linreg 'https://mcp.maatsii.com/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-maatsii-linreg": {
      "type": "http",
      "url": "https://mcp.maatsii.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-maatsii-linreg]
url = "https://mcp.maatsii.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-maatsii-linreg": {
      "type": "remote",
      "url": "https://mcp.maatsii.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-maatsii-linreg --url 'https://mcp.maatsii.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-maatsii-linreg:
    url: "https://mcp.maatsii.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-maatsii-linreg": {
      "Transport": "http",
      "Url": "https://mcp.maatsii.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-maatsii-linreg -t streamable-http -u 'https://mcp.maatsii.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 78, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `maatsii_get_chart` (~236 tokens)

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

Input parameters:

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

Output parameters:

- `charts` (array)
- `degraded` (boolean)
- `omitted` (array)

### `maatsii_get_group` (~355 tokens)

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.

Input parameters:

- `group` (string, required): Group name or alias, e.g. NQ, BTC, GOLD, VIX, PLTR, CREDIT
- `ids` (array): Only these chart ids from the group, e.g. ["c1","c4"]
- `image_mode` (string): "both" (default) = JPEG inline + url in text; "inline" = same; "url_only" = no image bytes, url only
- `include_images` (boolean): Default true. false is equivalent to image_mode 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.

Output parameters:

- `charts` (array)
- `degraded` (boolean)
- `omitted` (array)

### `maatsii_chart_map` (~95 tokens)

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.

### `maatsii_list_setups` (~245 tokens)

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.

Input parameters:

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

### `maatsii_match_setup` (~361 tokens)

Maatsii Match Setup (hint)

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.

Input parameters:

- `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).
- `timeframes` (array): Intervals of the charts the features were read from, e.g. ["100T","15M","1H"]. Required for TICK setup eligibility.
- `vision_features` (object, required): Boolean structure flags (fan_support_test, pullback_to_fan, tick_absorption, ...), dominant_bias, raw_vision_text, optional conditions[] — see the vision_features concept

### `maatsii_get_setup` (~144 tokens)

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.

Input parameters:

- `id` (string|number, required): Setup id, e.g. "#19", 19, or "T1"

### `maatsii_reading_guide` (~96 tokens)

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.

### `maatsii_analysis_framework` (~80 tokens)

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.

### `maatsii_fan_guide` (~98 tokens)

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_concept` (~105 tokens)

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.

Input parameters:

- `concept` (string, required): Concept name, e.g. 'playbook fields' or 'catalog direction'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-maatsii-linreg/mcp#diagnostics

## Score history

- 2026-09-25: 78
- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67

## Common questions

### What is the Maatsii MCP server?

Maatsii is an MCP server listed in the public MCP registry as com.maatsii/linreg. Live LinReg fan charts, 64-setup playbook, 11-section MTF TA. Remote MCP, no API key. This page covers its hosted endpoint (https://mcp.maatsii.com/mcp).

### Is the Maatsii MCP server safe to use?

Maatsii scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Maatsii MCP server expose?

Maatsii exposes 10 tools: maatsii_get_chart, maatsii_get_group, maatsii_chart_map, maatsii_list_setups, maatsii_match_setup, and 5 more. Their descriptions and schemas cost roughly 1,815 tokens of context every time the server is loaded.

### Does the Maatsii MCP server require authentication?

No. We connected to Maatsii without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Maatsii MCP server still maintained?

Maatsii is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.maatsii.com/mcp
- Repository: https://github.com/BL3IP/maatsii-cursor-plugin
- Website: https://maatsii.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-maatsii-linreg/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-maatsii-linreg/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-maatsii-linreg/mcp