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.

xStocker

NPM · @XSTOCKER/MCP

Build buy/sell orders for tokenized US stocks (xStocks) on Solana. Non-custodial.

Available components

65 Trust /100

Last scanned (2 hours ago)

Scores higher than 37% 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 549 tokens (~137/item across 4 items; 4 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 Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% 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 4 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.

  • 14 Oct 26 +32
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 88 functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
  • 12 Oct 26 33

    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 17 Oct 2026 · Analysed npm/@xstocker/mcp@0.2.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 94 packages
Packages resolved 94
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~549 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
build_order ~330

Build (NOT execute) a buy or sell order for an xStock. Nothing is traded and no funds move: this returns a quote (details) and a Solana Pay link (solanaPayUrl). Show the details (amount in, expected out, fee) to the user and give them the link or QR code: their wallet opens it and they approve there with their OWN wallet. For a buy, `amount` is how much pay_token to spend. For a sell, `amount` is how many xStock to sell, in the units the wallet shows (up to 8 decimals), or "max" to sell the entire balance. If a referral partner is configured on this server, details.partnerFee shows the extra fee paid to that partner. xStocks are issued by Backed Finance AG and are NOT available to U.S. citizens or residents. Trading tokenized equities involves risk of loss.

NameTypeReqDescription
amount–yesBuy: amount of pay_token to spend. Sell: amount of the xStock to sell in wallet units (number or decimal string, up to 8 decimals), or "max" to sell the whole balance.
assetstringyesxStock ticker from list_assets, e.g. "NVDAx"
include_transactionboolean–Also return the base64 unsigned transaction. Only for agents that have their own wallet signer.
pay_tokenstring–The non-xStock side of the trade
sidestring––
walletstringyesThe user's Solana wallet address (public address only, never a private key)

No output schema declared.

No examples provided.

check_partner ~104

Check that a wallet can receive referral fees. There is no registration: a partner is just a Solana wallet address, set on this server with XSTOCKER_PARTNER_WALLET. USDC fees land in the wallet's USDC token account (it must exist), SOL fees in the wallet itself. Only use if the user asks about becoming a partner.

NameTypeReqDescription
walletstringyesThe user's Solana wallet address (public address only, never a private key)

No output schema declared.

No examples provided.

get_order_status ~42

Check whether a signed and broadcast Solana transaction landed (processed/confirmed/finalized/failed/not_found).

NameTypeReqDescription
signaturestringyesSolana transaction signature

No output schema declared.

No examples provided.

list_assets ~73

List tradable tokenized stocks/ETFs (xStocks) on Solana with tickers and accepted pay tokens. Call this before build_order to get valid asset symbols. xStocks are issued by Backed Finance AG and are NOT available to U.S. citizens or residents. Trading tokenized equities involves risk of loss.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the xStocker MCP server?

xStocker runs locally as an npm package, launched with npx -y @xstocker/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 · @xstocker/mcp

# add to Claude Code
claude mcp add com-xstocker-agent-mcp -- npx -y @xstocker/mcp
Common questions

What is the xStocker MCP server?

xStocker is an MCP server listed in the public MCP registry as com.xstocker/agent-mcp. Build buy/sell orders for tokenized US stocks (xStocks) on Solana. Non-custodial. This page covers its npm package (@xstocker/mcp).

Is the xStocker MCP server safe to use?

xStocker scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 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 xStocker MCP server expose?

xStocker exposes 4 tools: list_assets, build_order, get_order_status, check_partner. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.

Is the xStocker MCP server still maintained?

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

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