T Invest (human-turn) MCP Server

t-invest-mcp npm v0.2.1 Source verified

Published by human-turn — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for T-Invest API (Tinkoff Investments): portfolio, market data, dividends, bonds, fundamentals, optional trading and sandbox

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([download_history_archive, get_history_archive_years, download_trades_archive]) co-exist with external-action tools ([download_history_archive]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_history_archive, get_history_archive_years, download_trades_archive] → sinks [download_history_archive]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow download_history_archive → download_history_archive

Tools 25

Each tool and what it can reach — statically extracted from the published source.

  • download_history_archiveingests untrusted inputnetwork egress
  • download_trades_archiveingests untrusted input
  • get_history_archive_yearsingests untrusted input
  • cancel_orderno sensitive capability
  • find_instrumentno sensitive capability
  • get_accountsno sensitive capability
  • get_accrued_interestsno sensitive capability
  • get_active_ordersno sensitive capability
  • get_asset_fundamentalsno sensitive capability
  • get_bond_couponsno sensitive capability
Show 15 more tools ↓
  • get_bond_eventsno sensitive capability
  • get_candlesno sensitive capability
  • get_dividendsno sensitive capability
  • get_forecastsno sensitive capability
  • get_instrumentno sensitive capability
  • get_last_pricesno sensitive capability
  • get_operationsno sensitive capability
  • get_order_bookno sensitive capability
  • get_portfoliono sensitive capability
  • get_server_infono sensitive capability
  • get_trading_schedulesno sensitive capability
  • place_orderno sensitive capability
  • sandbox_close_accountno sensitive capability
  • sandbox_open_accountno sensitive capability
  • sandbox_pay_inno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.1 latest A 97/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/t-invest-mcp/badge.svg)](https://mcptrustchecker.com/registry/t-invest-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/t-invest-mcp"><img src="https://mcptrustchecker.com/registry/t-invest-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/t-invest-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan t-invest-mcp --online

Use the free API → How scoring works

Other implementations of T Invest 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Finance & Commerce