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.

CoreForge Trading

NPM · COREFORGE-TRADING-MCP

CoreForge trading analytics: signals, backtests, risk, Greeks, token data. x402 pay-per-call.

0 this week 59 Trust /100

Last scanned (14 hours ago)

Scores higher than 29% of npm servers

Category Finance and Payments

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1647 tokens (~117/item across 14 items; 14 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 9 Nov 26 59

    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 21 Nov 2026 · Analysed npm/coreforge-trading-mcp@1.0.1

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 113 packages
Packages resolved 113
Stale 30
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,647 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
catalyst_classify ~109

Classify headlines into market-catalyst categories (earnings, merger/acquisition, buyback, dividend, guidance, restructuring, regulatory, legal, news), shaped as events with any tickers you attach. Classification only — no direction or outcome prediction. Paid via x402 ($0.01 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
headlinesarrayyesUp to 50 headlines, as strings or {headline, tickers} objects

No output schema declared.

No examples provided.

chain_balance ~56

Base chain read: native ETH balance of an address. Paid via x402 ($0.002 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
addressstringyes0x address

No output schema declared.

No examples provided.

chain_block ~49

Base chain read: latest block number, hash, timestamp and transaction count. Paid via x402 ($0.001 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chain_gas ~48

Base chain read: current gas price (wei and gwei). Paid via x402 ($0.001 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chain_token_balance ~86

Base chain read: ERC-20 token balance of an address, with the token's symbol and decimals resolved on-chain. Paid via x402 ($0.003 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
addressstringyes0x wallet address
tokenstringyes0x ERC-20 contract address

No output schema declared.

No examples provided.

gov_contracts ~144

Recent US federal contract awards (contract types A–D) from the public USAspending.gov API, deduplicated and largest-first, with recipient names resolved to tickers where a confident match exists. Public data, repackaged. Paid via x402 ($0.02 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
daysinteger–Lookback window in days (default 30)
limitinteger–Max awards (default 25)
minAmountnumber–Minimum obligated amount in USD (default 1000000)
tickerstring–Only awards resolved to this ticker

No output schema declared.

No examples provided.

options_greeks ~229

Black-Scholes model computation (no live quotes): either a generated option chain for an expiry, or multi-leg payoff analysis (max loss/profit, breakevens, net premium) with per-leg Greeks. Model values from inputs, not a recommendation. Paid via x402 ($0.02 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
expiryDatestring–Chain expiry, YYYY-MM-DD (chain mode; or use expiryDays)
expiryDaysinteger–Days to expiry (default 30)
ivnumber–Implied volatility as a decimal (default 0.25)
legsarray–Legs mode: 1–8 option legs to analyse as one strategy
riskFreeRatenumber–Risk-free rate as a decimal (default 0.0525)
strikesarray–Chain strikes (default: 9 strikes around the underlying)
symbolstring–Underlying symbol label (chain mode)
underlyingPricenumberyesCurrent underlying price

No output schema declared.

No examples provided.

portfolio_risk ~160

Portfolio risk computation: per-holding and portfolio volatility, Sharpe, Sortino, max drawdown, VaR/CVaR, correlation and concentration analysis; optional predefined-scenario stress tests and Monte Carlo distribution. Bars are fetched per symbol unless you supply closes/bars per holding. Computed data, not a recommendation. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
holdingsarrayyes2–20 holdings, each with dollarValue or weight
monteCarloboolean–Add the Monte Carlo distribution
stressboolean–Run the predefined stress scenarios
totalValuenumber–Total portfolio value (used with weights)

No output schema declared.

No examples provided.

token_analytics ~102

Token market-data bundle from public DEX data: price, FDV/market cap, liquidity, volume windows, 24h transactions, pair list and market age. Raw data — no scores or opinions. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
addressstringyesToken address: an EVM 0x… contract address or a Solana mint address

No output schema declared.

No examples provided.

trading_backtest ~163

Historical rule-set evaluation over daily bars: net return, win rate, max drawdown and trade count for the latest window (in-sample) and the window before it (out-of-sample walk-forward); optional Monte Carlo block-resample distribution. Computed data, not a performance promise. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
monteCarloboolean–Add the Monte Carlo distribution (500 simulations)
strategystringyesRule set to evaluate
symbolstring–One symbol (or use symbols)
symbolsarray–Up to 10 symbols
windowDaysinteger–Window length in days (default 90)

No output schema declared.

No examples provided.

trading_indicators ~196

Technical-indicator computation (SMA, EMA, RSI, MACD, Bollinger Bands, plus the ensemble state) on bars you supply — no external data fetch. Computed data, not a recommendation. Paid via x402 ($0.01 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
barsarray–OHLCV bars (10–5000); each needs at least a close
closesarray–Close prices only (alternative to bars)
emaPeriodsarray–EMA periods (default 12, 26)
rsiPeriodinteger–RSI period (default 14)
seriesboolean–Also return the full indicator series, not just the latest values
smaPeriodsarray–SMA periods (default 20, 50, 200)
symbolstring–Label for the series

No output schema declared.

No examples provided.

trading_regime ~72

Market-regime classification (9 states) computed from universe breadth, trend and volatility, with the per-regime strategy-weight table and a summary. Computed data, not a recommendation. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trading_signal ~156

Deterministic strategy-state computation for one symbol: the current state of five published rule sets (ma_crossover, rsi_mean_reversion, momentum, leveraged_momentum, macd_crossover) plus an ensemble state over daily bars; BTC/ETH/SOL also carry a Coinversa sentiment block. Computed data, not a recommendation. Paid via x402 ($0.02 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
strategystring–Return only this one strategy's state
symbolstringyesSymbol, e.g. SPY, AAPL, BTC, ETH, SOL (16 equities/ETFs + BTC/ETH/SOL in the core universe)

No output schema declared.

No examples provided.

trading_signals_board ~77

Full-universe strategy-state snapshot: all 16 equities/ETFs plus BTC, ETH and SOL, each with the five rule-set states and an ensemble state. Computed data, not a recommendation. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the CoreForge Trading MCP server?

CoreForge Trading runs locally as an npm package, launched with npx -y coreforge-trading-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · coreforge-trading-mcp

# add to Claude Code
claude mcp add shaficodes25-coreforge-trading -- npx -y coreforge-trading-mcp
Common questions

What is the CoreForge Trading MCP server?

CoreForge Trading is an MCP server listed in the public MCP registry as io.github.ShafiCodes25/coreforge-trading. CoreForge trading analytics: signals, backtests, risk, Greeks, token data. x402 pay-per-call. This page covers its npm package (coreforge-trading-mcp).

Is the CoreForge Trading MCP server safe to use?

CoreForge Trading scores 59 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 CoreForge Trading MCP server expose?

CoreForge Trading exposes 14 tools: trading_signal, trading_signals_board, trading_regime, trading_backtest, trading_indicators, and 9 more. Their descriptions and schemas cost roughly 1,647 tokens of context every time the server is loaded.

Is the CoreForge Trading MCP server still maintained?

CoreForge Trading is still listed as active in the MCP registry. We last reached this channel on 21 November 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 CoreForge Trading MCP server under?

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

What did VerifyMCP test on the CoreForge Trading MCP server?

VerifyMCP ran 14 checks on CoreForge Trading, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about CoreForge Trading: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.