# QSignals AI Stock Scores (remote · qsignals.ai)

Stock scores (0-100) and signals for any US stock, with full AI analysis for 83 AI-related names.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `qsignals.ai`: 73/100 (this document), [markdown](https://verifymcp.io/servers/jiahongq-qsignals/api-mcp.md), [page](https://verifymcp.io/servers/jiahongq-qsignals/api-mcp)

## Channel facts

- Endpoint: `https://qsignals.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 453 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the QSignals AI Stock Scores MCP server?

QSignals AI Stock Scores is a hosted endpoint at https://qsignals.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http jiahongq-qsignals 'https://qsignals.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jiahongq-qsignals": {
      "url": "https://qsignals.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jiahongq-qsignals": {
      "type": "http",
      "url": "https://qsignals.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jiahongq-qsignals]
url = "https://qsignals.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jiahongq-qsignals": {
      "type": "remote",
      "url": "https://qsignals.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jiahongq-qsignals --url 'https://qsignals.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jiahongq-qsignals:
    url: "https://qsignals.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jiahongq-qsignals": {
      "Transport": "http",
      "Url": "https://qsignals.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jiahongq-qsignals -t streamable-http -u 'https://qsignals.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jiahongq-qsignals": {
      "type": "http",
      "url": "https://qsignals.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 72)

First indexed and scored.

## MCP tools (6)

### `list_covered_stocks` (~41 tokens)

List the 83 curated AI, space, energy and robotics stocks and ETFs. These get the full QSignals score, including the AI strategic analysis.

### `get_stock_score` (~80 tokens)

Get the QSignals score (0-100) and signal for one stock or ETF across short, mid and long horizons, with a one-line reason for each. Curated stocks get the full score; any other US ticker gets a technical-only score (Pro).

Input parameters:

- `ticker` (string, required): Ticker symbol, e.g. NVDA or SHOP

### `get_all_scores` (~76 tokens)

Get scores for every curated stock on your plan in one call, sorted by the chosen horizon. Use this instead of calling get_stock_score once per stock.

Input parameters:

- `sort_by` (string): Horizon to sort by (default short). short = about 1 week, mid = about 1 month, long = about 6 months

### `get_top_picks` (~87 tokens)

Get the highest- or lowest-scored stocks for a horizon. Pro keys only.

Input parameters:

- `horizon` (string, required): short = about 1 week, mid = about 1 month, long = about 6 months
- `limit` (integer): How many stocks to return (default 5)
- `side` (string): top = highest scores (default), bottom = lowest

### `get_market_regime` (~34 tokens)

Get the current market regime for tech stocks (bullish, neutral or bearish), based on QQQ trend and momentum.

### `get_track_record` (~42 tokens)

Get how past QSignals scores performed: hit rate, average return of the top 10 vs bottom 10 picks, and performance vs QQQ, per horizon.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jiahongq-qsignals/api-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72

## Common questions

### What is the QSignals AI Stock Scores MCP server?

QSignals AI Stock Scores is an MCP server listed in the public MCP registry as io.github.jiahongq/qsignals. Stock scores (0-100) and signals for any US stock, with full AI analysis for 83 AI-related names. This page covers its hosted endpoint (https://qsignals.ai/api/mcp).

### Is the QSignals AI Stock Scores MCP server safe to use?

QSignals AI Stock Scores scores 73 out of 100 on VerifyMCP. 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 QSignals AI Stock Scores MCP server expose?

QSignals AI Stock Scores exposes 6 tools: list_covered_stocks, get_stock_score, get_all_scores, get_top_picks, get_market_regime, get_track_record. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.

### Does the QSignals AI Stock Scores MCP server require authentication?

No. We connected to QSignals AI Stock Scores without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the QSignals AI Stock Scores MCP server still maintained?

QSignals AI Stock Scores is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://qsignals.ai/api/mcp
- Authorisation metadata: https://qsignals.ai/.well-known/oauth-protected-resource/api/mcp
- Website: https://qsignals.ai/developers
- Changelog RSS feed: https://verifymcp.io/servers/jiahongq-qsignals/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jiahongq-qsignals/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jiahongq-qsignals/api-mcp