io.github.nirajagarwal/stox-mcp
REMOTE · MCP.STOX.MARKET · SCANNED SEP 22
Percentile fingerprints, curated peers, theme clusters & market-stress context for US stocks.
Available components
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 921 tokens (~153/item across 6 items; 6 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% 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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.nirajagarwal/stox-mcp server?
io.github.nirajagarwal/stox-mcp is a hosted endpoint at https://mcp.stox.market/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 · mcp.stox.market
claude mcp add --transport http nirajagarwal-stox-mcp 'https://mcp.stox.market/mcp'
{
"mcpServers": {
"nirajagarwal-stox-mcp": {
"url": "https://mcp.stox.market/mcp"
}
}
} {
"servers": {
"nirajagarwal-stox-mcp": {
"type": "http",
"url": "https://mcp.stox.market/mcp"
}
}
} [mcp_servers.nirajagarwal-stox-mcp] url = "https://mcp.stox.market/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirajagarwal-stox-mcp": {
"type": "remote",
"url": "https://mcp.stox.market/mcp",
"enabled": true
}
}
} openclaw mcp add nirajagarwal-stox-mcp --url 'https://mcp.stox.market/mcp' --transport streamable-http
mcp_servers:
nirajagarwal-stox-mcp:
url: "https://mcp.stox.market/mcp" {
"McpServers": {
"nirajagarwal-stox-mcp": {
"Transport": "http",
"Url": "https://mcp.stox.market/mcp"
}
}
} assistant mcp add nirajagarwal-stox-mcp -t streamable-http -u 'https://mcp.stox.market/mcp'
{
"mcpServers": {
"nirajagarwal-stox-mcp": {
"type": "http",
"url": "https://mcp.stox.market/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://mcp.stox.market/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.stox.market | CN=YE2,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 64b2d1b2daed0ad1a4a2f9f1ec34dd1a2cc |
| SANs: mcp.stox.market | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.stox.market. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| market. | present | 40531 | 8 | Verified |
| stox.market. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.stox.market/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.stox.market/mcp | HTTPS enforced | 301 | https://mcp.stox.market/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 →
compare Compare fingerprints side by side ~76
The 16 percentile scores + P3 + 1Y price change for 2-5 tickers as one compact matrix (rows = metrics, columns = tickers). Use when weighing names against each other; percentiles make the comparison fair across sectors and sizes.
| Name | Type | Req | Description |
|---|---|---|---|
| tickers | array | yes | 2-5 US tickers |
No output schema declared.
No examples provided.
fingerprint Stock percentile fingerprint ~139
The character of one stock in ~550 tokens: 16 percentile scores (vs the S&P 500 cohort) across four panels — Market Beat, Trend Persistence, Business Growth, Pressure (money flow) — plus the composite P3 score (the validated 3-factor form), curated competitive peers (not GICS), a one-line character read, and the price line. Use for 'is this number good?' and quick company character.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | RESERVED (phase 2): YYYY-MM-DD point-in-time snapshot; currently only the live snapshot is served |
| ticker | string | yes | US ticker, e.g. NVDA |
No output schema declared.
No examples provided.
market_regime Market stress context ~94
Where market stress sits right now: the dashboard's 8-indicator stance, each indicator's traffic-light band, the VIX 5-year percentile (the ONE input validated as predicting forward risk — blended composites tested worse), and the S2 stress-confirmation badge (SPY below its 40-week average AND VIX above its 80th percentile of the trailing year). Descriptive context, not a market call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
peers Curated competitive peers ~78
The stock's TRUE competitive cluster — LLM-curated from segment overlap (who it actually competes with for revenue), not GICS classification. Costco's peers are WMT/TGT/KR, not 'Discount Stores'. Each peer carries its P3 score. Honest empty list for monopolies/private-rival cases.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
screen Metric screen (P3-sorted, min/max on all 16 scores) ~310
Screen the S&P 500 + NDX universe on ANY of the 16 percentile scores, with minimum AND maximum bounds, optionally within one GICS sector, sorted by the validated P3 composite or by any single metric. Metric keys: marketBeat1Y/1M/1W/1D (price vs SPY), rankPersistence52W/26W/13W + trendPersistence (rank stability), businessBeat + revGrowthYoy + marginGrowthYoy + fcfGrowthYoy (business growth), accumDistFlow/30/5/2 (money flow 60/30/5/2-day). Examples: momentum — {sort_by:'marketBeat1M', filters:[{metric:'businessBeat', min:70}]}; fallen leaders — {filters:[{metric:'rankPersistence52W', min:80},{metric:'marketBeat1Y', max:40}]}. Legacy min_perform/min_persist/min_profit/min_pressure still work (the four headline scores).
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | bounds on any metrics; entries AND together |
| min_perform | number | – | – |
| min_persist | number | – | – |
| min_pressure | number | – | – |
| min_profit | number | – | – |
| n | number | – | max results (default 12) |
| sector | string | – | GICS sector filter, e.g. 'Energy' |
| sort_by | string | – | 'p3' (default) or any metric key; descending |
No output schema declared.
No examples provided.
theme_cluster Co-movement theme cluster ~93
The statistical theme a stock actually trades with: clusters built from years of price co-movement (market-removed residuals → random-matrix cleaning → Ward linkage), not sector labels. Returns the cluster's name, description, cohesion, sector mix and up to 20 member tickers. Different question from `peers` (business competition) — this is who it MOVES with.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.nirajagarwal/stox-mcp server?
io.github.nirajagarwal/stox-mcp is listed in the public MCP registry as io.github.nirajagarwal/stox-mcp. Percentile fingerprints, curated peers, theme clusters & market-stress context for US stocks. This page covers its hosted endpoint (https://mcp.stox.market/mcp).
Is the io.github.nirajagarwal/stox-mcp server safe to use?
io.github.nirajagarwal/stox-mcp scores 80 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 io.github.nirajagarwal/stox-mcp server expose?
io.github.nirajagarwal/stox-mcp exposes 6 tools: fingerprint, compare, peers, theme_cluster, screen, market_regime. Their descriptions and schemas cost roughly 790 tokens of context every time the server is loaded.
Does the io.github.nirajagarwal/stox-mcp server require authentication?
No. We connected to io.github.nirajagarwal/stox-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.nirajagarwal/stox-mcp server still maintained?
io.github.nirajagarwal/stox-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.