Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TASignal

NPM · @AGENTGATE-BUILDER/TASIGNAL · 2 COMPONENTS

Read-only crypto indicators, risk sizing and rule backtests. Not financial advice.

46 Trust /100

Last scanned (6 hours ago)

Scores higher than 28% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 496 tokens (~165/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Oct 26 46

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Oct 2026 · Analysed npm/@agentgate-builder/tasignal@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~449 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ta_backtest ~172

Paid only (needs TASIGNAL_X402_PRIVATE_KEY, $0.05 USDC on Base per call): sma_cross, ema_cross, rsi_reversion, breakout or macd_cross on up to 2000 candles with fees; return vs buy-and-hold, drawdown, Sharpe, win rate, trades. Historical simulation; past performance does not guarantee future results.

NameTypeReqDescription
barsinteger––
directionstring––
fastinteger––
fee_bpsnumber––
periodinteger––
slowinteger––
strategystringyes–
symbolstringyesAsset ticker, e.g. BTC, ETH, SOL, HYPE
timeframestring–Candle timeframe (default 1h)

No output schema declared.

No examples provided.

ta_indicators ~135

Technical read for a crypto asset on closed candles. Free by default: bias (strong bearish ... strong bullish), trend and regime. With TASIGNAL_X402_PRIVATE_KEY set, returns the paid lite tier ($0.005 USDC on Base per call over x402): RSI, MACD, EMA 20/50/200, Bollinger, ATR, ADX, stochastic, realized volatility and the bias components. Read-only; not financial advice.

NameTypeReqDescription
symbolstringyesAsset ticker, e.g. BTC, ETH, SOL, HYPE
timeframestring–Candle timeframe (default 1h)

No output schema declared.

No examples provided.

ta_position_size ~142

Paid only (needs TASIGNAL_X402_PRIVATE_KEY, $0.02 USDC on Base per call): historical VaR/CVaR, drawdowns, volatility, Sharpe/Sortino, ATR stop and position size for account_usd at risk_pct. Read-only; not financial advice.

NameTypeReqDescription
account_usdnumber––
entrynumber––
risk_pctnumber––
sidestring––
stopnumber––
symbolstringyesAsset ticker, e.g. BTC, ETH, SOL, HYPE
timeframestring–Candle timeframe (default 1h)

No output schema declared.

No examples provided.

Install

How do I install the TASignal MCP server?

TASignal runs locally as an npm package, launched with npx -y @agentgate-builder/tasignal. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @agentgate-builder/tasignal

# add to Claude Code
claude mcp add co-youraitools-tasignal -- npx -y @agentgate-builder/tasignal
Common questions

What is the TASignal MCP server?

TASignal is an MCP server listed in the public MCP registry as co.youraitools/tasignal. Read-only crypto indicators, risk sizing and rule backtests. Not financial advice. This page covers its npm package (@agentgate-builder/tasignal).

Is the TASignal MCP server safe to use?

TASignal scores 46 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. 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 TASignal MCP server expose?

TASignal exposes 3 tools: ta_indicators, ta_position_size, ta_backtest. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.

Is the TASignal MCP server still maintained?

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

What licence is the TASignal MCP server under?

TASignal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.