com.ou-reports/just-signal
NPM · JUST-SIGNAL-MCP · 2 COMPONENTS · SCANNED SEP 25
Keyless MCP for Just Signal: live quotes, report publishing, scorecard, and Chophouse panel grades.
Available components
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 62 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 517 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_report" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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 com.ou-reports/just-signal MCP server?
com.ou-reports/just-signal runs locally as an npm package, launched with npx -y just-signal-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 · just-signal-mcp
claude mcp add com-ou-reports-just-signal -- npx -y just-signal-mcp
{
"mcpServers": {
"com-ou-reports-just-signal": {
"command": "npx",
"args": [
"-y",
"just-signal-mcp"
]
}
}
} {
"servers": {
"com-ou-reports-just-signal": {
"command": "npx",
"args": [
"-y",
"just-signal-mcp"
]
}
}
} codex mcp add com-ou-reports-just-signal -- npx -y just-signal-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ou-reports-just-signal": {
"type": "local",
"command": [
"npx",
"-y",
"just-signal-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-ou-reports-just-signal --command npx --arg -y --arg just-signal-mcp
mcp_servers:
com-ou-reports-just-signal:
command: "npx"
args: ["-y", "just-signal-mcp"] {
"McpServers": {
"com-ou-reports-just-signal": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"just-signal-mcp"
]
}
}
} assistant mcp add com-ou-reports-just-signal -t stdio -c npx -a -y just-signal-mcp
{
"mcpServers": {
"com-ou-reports-just-signal": {
"command": "npx",
"args": [
"-y",
"just-signal-mcp"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −2
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 25 Sept 2026 · Analysed npm/just-signal-mcp@1.3.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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_panel_grade Get the Chophouse panel grade ~135
The Investment Panel's read on one ticker: its Chophouse 'doneness' grade (RAW…CHARRED — how much value is already cooked in) plus every seat's vote across 11 emulated investor lenses (Buffett, Dalio, Ackman, Einhorn, Tepper, Druckenmiller, Cohen, Platt, Williams, Deutscher, CryptoLifer), with the registry verdict for context. The panel advises; the reader decides. If a ticker isn't plated yet, says so and points to Ask the Kitchen.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | US ticker symbol, e.g. NVDA |
No output schema declared.
No examples provided.
get_scorecard Get the Signal Scorecard ~89
Audit past signals. Reads the ticker registry (the master list the website scores) and grades EVERY ticker with the unified verdict cascade (projection › direction › return): AHEAD / TRACKING / BEHIND, pro-rated by elapsed time, against the daily snapshot close — zero live quote calls, identical to the website. Includes the Chophouse doneness grade where the panel has plated a ticker.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stock_quote Get live stock quote ~72
Fetch a live stock/ETF quote (current price + % change) through Just Signal's server-side Finnhub relay. Use this to establish the Day-0 baseline price for a ticker before writing projections.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | US ticker symbol, e.g. NVDA, TSLA, FLNC |
No output schema declared.
No examples provided.
list_reports List published reports ~29
List recent Just Signal reports from the public library (newest first).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
publish_report Publish a Just Signal briefing ~192
Ground, render, and PUBLISH a complete Just Signal briefing to the public library at ou-reports.com. The SERVER grounds every ticker's live Day-0 price, computes exact dollar targets from your percentage projections, renders the report, and stores it — so publishing is open to the community with no API key: tokenless callers are rate-limited per day; set JS_PUBLISH_TOKEN to bypass. Provide targets ONLY as % ('+18%') or multiples ('2.5x'), never dollars. Returns the published URL. 5 trends is the standard briefing.
| Name | Type | Req | Description |
|---|---|---|---|
| briefingTitle | string | yes | – |
| durationSeconds | number | – | Optional: seconds the client spent generating, for the Time-Out Timer stamp. Defaults to 0. |
| executiveSummary | string | yes | – |
| sectors | string | yes | Short topic label, e.g. 'grid-scale energy storage' |
| trends | array | yes | – |
No output schema declared.
No examples provided.
What is the com.ou-reports/just-signal MCP server?
com.ou-reports/just-signal is an MCP server listed in the public MCP registry as com.ou-reports/just-signal. Keyless MCP for Just Signal: live quotes, report publishing, scorecard, and Chophouse panel grades. This page covers its npm package (just-signal-mcp).
Is the com.ou-reports/just-signal MCP server safe to use?
com.ou-reports/just-signal scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 com.ou-reports/just-signal MCP server expose?
com.ou-reports/just-signal exposes 5 tools: get_stock_quote, publish_report, list_reports, get_scorecard, get_panel_grade. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Is the com.ou-reports/just-signal MCP server still maintained?
com.ou-reports/just-signal is still listed as active in the MCP registry. We last reached this channel on 25 September 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 com.ou-reports/just-signal MCP server under?
com.ou-reports/just-signal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.