mcpbeat Sign in

Maatsii MCP Server

answering

Maatsii is answering right now. Last checked 9 min ago. It exposes 10 tools. Last commit 22 Sep 2026.

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

Uptime history 69 days of history · worst day 99%
69 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
358 ms
Response time
average over 24h
0
Stars
last commit 22 Sep 2026

Nothing serious here today

Today is the operative word: we check Maatsii every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add linreg --transport http https://mcp.maatsii.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.maatsii.com/mcp
~/.codex/config.toml
[mcp_servers.linreg]
url = "https://mcp.maatsii.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "linreg": {
      "url": "https://mcp.maatsii.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "linreg": {
      "type": "http",
      "url": "https://mcp.maatsii.com/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

maatsii
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_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_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 truth for symbol+timeframe; prices are read off the RIGHT AXIS (maatsii_reading_guide).
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.
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.
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.
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.
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) 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.
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.maatsii.com/mcp streamable-http answering 368 ms 9 min ago

Alternatives to Maatsii

same job, measured the same way
Deezer MCP by UnClick
by malamutemayhem

Search Deezer tracks, artists, albums, playlists, charts, and podcasts. No API key. By UnClick.

50 installs/wk local only
PostData
by postdata

No-signup IoT backend: device names, sensor readings, history and live charts. No API key needed.

6 tools answering
Astral MCP
by davidmosiah

Precision-audited astrology MCP: natal charts, transits, synastry, moon phases. No API key.

99 installs/wk local only
SkyAccess
by skyaccess

Search 5,000+ live empty leg flights, get charter estimates and booking links. Free, no API key.

38 installs/wk 6 tools answering
App Store + Google Play Data
by thevalkdokk

Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts.

85 installs/wk 5 tools answering
Binance Market MCP
by mrfentmen

Live crypto prices, tickers, and candlestick charts from Binance public data. No key required.

171 installs/wk local only
R
Revmng MCP
by arikanatakan

Revenue-management tools for AI agents: seat protection, overbooking, pricing, bid prices, charts.

139 installs/wk local only
Dofek
by asherlc

Private health and fitness analytics through a secure remote MCP connection.

answering

Maatsii — questions

Answers built from our own checks of this server.

What can Maatsii do?
It exposes 10 tools, read directly from the server on our last check. Among them: maatsii_analysis_framework, maatsii_chart_map, maatsii_fan_guide, maatsii_get_chart, maatsii_get_concept, maatsii_get_group and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Maatsii working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 358 ms. The bar chart above shows every period we have measured.
How do I connect Maatsii?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Maatsii need an API key?
No. Maatsii completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Maatsii?
It answers our handshake in 358 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Maatsii open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.maatsii.com, which runs on its operator's own terms.