Stock Trends Remote MCP

What agents can use today

• What is it?A semantic and discovery interface for MCP-compatible agents over API-backed Stock Trends context.
• What is the URL?https://mcp.stocktrends.com/mcp
• Do I need an API key?No. Connecting, discovery, resources, and the three free tools are credential-free. Paid remote tools use x402 payment authorization instead of a subscription API key.
• Can an ordinary MCP client run paid tools?Only if it implements this MCP payment exchange and can obtain payment authorization. Connecting alone does not authorize or automate paid execution.

The API remains authoritative

1. Source

   Stock Trends API

   The authoritative contract for endpoint behavior, request schemas, pricing, payment requirements, and market intelligence.

2. Adapter

   Stock Trends MCP

   A thin adapter that exposes curated API-backed resources and tools with API provenance preserved.

3. Consumer

   MCP-compatible agent

   Connect remotely over Streamable HTTP or, when needed, launch the separate local stdio server.

Stock Trends API → Stock Trends MCP → MCP-compatible agent.

19 tools, 10 public resources, and no prompts

The public Remote MCP exposes the following credential-free resources. They are suitable for discovering and understanding Stock Trends before any premium API workflow.

Three free tools

stocktrends_estimate_workflow_cost plans workflow cost without paid execution. stocktrends_lookup_instruments finds public instrument candidates, and stocktrends_resolve_instrument resolves an instrument identifier before a paid symbol request. None requires an API key, payment authorization, or spend.

Twelve x402-paid GET tools

The paid GET surface provides API-authored ST-IM latest and history, indicators latest and history, base selections (not the published ST-IM Select list), market regime latest and history, sector breadth, leadership summary, top screener output, and Market Epoch latest and history.

Four x402-paid POST tools

These tools provide API-authored analytical context for agent research workflows. They do not execute trades, manage assets, or provide investment advice.

The Remote MCP registers 0 prompts. It does not forward a customer subscription API key or provide MPP through the public MCP. It is an API-backed adapter; the API remains authoritative for schemas, pricing, payment enforcement, settlement, and analytical responses.

Remote first; local stdio when your environment needs it

Use the public Streamable HTTP endpoint

Configure a remote-capable MCP client with this endpoint. The exact configuration field names vary by client, so use that client’s current remote-MCP documentation rather than treating this provider-neutral example as a client-specific file.

{
  "server": "Stock Trends Remote MCP",
  "transport": "streamable-http",
  "url": "https://mcp.stocktrends.com/mcp"
}

No Node.js installation or Stock Trends API key is required to connect to this public remote surface. Connection and discovery do not authorize paid execution.

Operational status endpoints: https://mcp.stocktrends.com/healthz and https://mcp.stocktrends.com/readyz.

Keep a local process only when you need local stdio behavior

The separately available local server is for clients that launch a process on the developer machine and for separately gated API-key configurations. It requires Node.js 20+.

npm install @stocktrends-publications/stocktrends-mcp-server

Generic local stdio configuration

{
  "command": "<path-to-your-project>/node_modules/.bin/stocktrends-mcp-server",
  "env": {}
}

On Windows, use node_modules\.bin\stocktrends-mcp-server.cmd. See the MCP server repository for current local installation and environment-variable guidance.

LOCAL STDIO ONLY: separately gated paid local configurations use subscription API-key calls to the REST API. This is distinct from the public Remote MCP, whose paid tools use x402. Optional default-off local x402 mode only relays approved HTTP 402 challenge metadata for inspection; it is not payment execution.

MCP transport is not a payment rail

Subscription, x402, and MPP remain distinct payment rails for applicable Stock Trends API usage. The public Remote MCP uses x402 for its sixteen paid tools; it does not make subscription or MPP available through the MCP endpoint.

For a paid remote tool, call it first without payment authorization to receive the API-authored payment requirements as MCP tool content. A payment-capable client must obtain an applicable authorization and submit it as MCP metadata under x402/payment. The adapter forwards the resulting payment-bearing API request with the upstream PAYMENT-SIGNATURE header, then returns upstream settlement metadata under x402/payment-response. These MCP metadata fields are not HTTP headers sent by the MCP client.

Payment authorization is arranged by the client or its payment infrastructure; the Remote MCP is not a wallet. Do not assume that connecting an ordinary MCP client makes payment automatic, or that an x402 REST client automatically implements this MCP-specific exchange. For current prices and API contracts, consult the authoritative OpenAPI schema and pricing catalog.

For POST tools, the adapter retains a pending challenge against the canonical request body in its own short-lived challenge state. This is not a claim that the EIP-3009 payment signature independently signs the analytical JSON body. If payment settlement is uncertain, do not automatically retry a payment-bearing tool call. A settled analytical API error can still be a paid request.

Inspect the underlying API contract

• Canonical API llms.txt — authoritative endpoint and API-contract guide
• OpenAPI schema — request and response contract
• Pricing catalog — current endpoint pricing
• MCP server repository — local server source and architecture notes

Important disclosures

Stock Trends provides structured market context and probabilistic research intelligence. Whether accessed through the REST API or MCP, its outputs are not investment advice, price targets, direct buy/sell commands, or guarantees of future performance.