Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Maatsii is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Live LinReg fan charts, 64-setup playbook, 11-section MTF TA. Remote MCP, no API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http maatsii-mcp https://mcp.maatsii.com/mcp
# 2 — ask your agent for something these tools do
# maatsii_get_chart, maatsii_get_group, maatsii_chart_map and 7 more
Maatsii costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 1 server
maatsii1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http maatsii-mcp https://mcp.maatsii.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_or_ticker | string | yes | Canonical id c1..c200, or a ticker like NQ_100T / BTCUSD / PLTR |
| cb | string | no | Optional cachebuster [A-Za-z0-9._-]{1,64}; a fresh one is generated if omitted or invalid |
| image_mode | string | no | "both" (default) = JPEG inline + url in text; "inline" = same; "url_only" = no image bytes, url only |
| include_images | boolean | no | Default true. false is equivalent to image_mode url_only. |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | yes | Group name or alias, e.g. NQ, BTC, GOLD, VIX, PLTR, CREDIT |
| ids | array | no | Only these chart ids from the group, e.g. ["c1","c4"] |
| max_images | integer | no | 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 | string | no | "both" (default) = JPEG inline + url in text; "inline" = same; "url_only" = no image bytes, url only |
| include_images | boolean | no | Default true. false is equivalent to image_mode url_only. |
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.
No parameter schema on file.
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-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | — |
| direction | string | no | — |
| timeframe | string | no | Filter to setups applicable on this interval, e.g. 1H or 100T |
| category | string | no | Filter by category slug, e.g. advanced_pattern, confluence, correlation_intermarket, divergence, ... |
| detail | string | no | "card" = catalog fields only; "full" (default) adds the playbook text |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vision_features | object | yes | Boolean structure flags (fan_support_test, pullback_to_fan, tick_absorption, ...), dominant_bias, raw_vision_text, optional conditions[] — see the vision_features concept |
| timeframes | array | no | Intervals of the charts the features were read from, e.g. ["100T","15M","1H"]. Required for TICK setup eligibility. |
| groups_read | array | no | Group aliases the client fetched this turn (e.g. ["NQ","VIX"]); used only to allow the vol-gated setup #78. |
| max_results | integer | no | 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). |
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. Ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string/number | yes | Setup id, e.g. "#19", 19, or "T1" |
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| concept | string | yes | Concept name, e.g. 'playbook fields' or 'catalog direction' |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Maatsii or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.5.2.
1.5.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Maatsii can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.