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.
Available components
Last scanned (5 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 453 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +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.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 72
First indexed and scored.
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 5 Nov 2026 · Probed https://qsignals.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qsignals.ai | CN=YR1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 54cafbdfd27bbdbd18342053fa95c1c3000 |
| SANs: qsignals.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of qsignals.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| qsignals.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://*.clerk.accounts.dev https://clerk.qsignals.ai https://challenges.cloudflare.com https://va.vercel-scripts.com https://us-assets.i.posthog.com https://www.googletagmanager.com https://googleads.g.doubleclick.net https://www.googleadservices.com; worker-src 'self' blob:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob:; connect-src 'self' https://*.clerk.accounts.dev https://clerk.qsignals.ai https://*.clerk.dev https://*.supabase.co https://api.stripe.com https://*.ingest.sentry.io https://*.ingest.us.sentry.io https://us.i.posthog.com https://us-assets.i.posthog.com https://www.googletagmanager.com https://www.google-analytics.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.google.com https://ad.doubleclick.net; font-src 'self' data:; frame-src https://*.clerk.accounts.dev https://clerk.qsignals.ai https://challenges.cloudflare.com https://checkout.stripe.com; frame-ancestors 'none'; object-s |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qsignals.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://qsignals.ai/api/mcp | HTTPS enforced | 308 | https://qsignals.ai/api/mcp |
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 →
get_all_scores ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sort_by | string | – | Horizon to sort by (default short). short = about 1 week, mid = about 1 month, long = about 6 months |
No output schema declared.
No examples provided.
get_market_regime ~34
Get the current market regime for tech stocks (bullish, neutral or bearish), based on QQQ trend and momentum.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stock_score ~80
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. NVDA or SHOP |
No output schema declared.
No examples provided.
get_top_picks ~87
Get the highest- or lowest-scored stocks for a horizon. Pro keys only.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon | string | yes | 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 |
No output schema declared.
No examples provided.
get_track_record ~42
Get how past QSignals scores performed: hit rate, average return of the top 10 vs bottom 10 picks, and performance vs QQQ, per horizon.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_covered_stocks ~41
List the 83 curated AI, space, energy and robotics stocks and ETFs. These get the full QSignals score, including the AI strategic analysis.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · qsignals.ai
claude mcp add --transport http jiahongq-qsignals 'https://qsignals.ai/api/mcp'
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.