mcp server
just-signal
Keyless MCP for Just Signal: live quotes, report publishing, scorecard, and Chophouse panel grades.
Description as published by the maintainer. Source
- version 1.3.0
- active
active — Registry entry last updated 2026-07-25.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_panel_grade(ticker)- 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, with the registry verdict for context. The panel advises, the reader decides. Says so if the ticker is not plated yet. Required: ticker.
get_scorecard- Audit past signals: projected vs actual return for every grounded ticker, graded AHEAD / TRACKING / BEHIND, pro-rated by elapsed time.
get_stock_quote(ticker)- Live stock/ETF quote (price + % change) via Just Signal's market-data relay. Establishes a ticker's Day-0 baseline before projecting. Required: ticker.
list_reports(limit)- List recent Just Signal reports from the public library (newest first).
publish_report(token, trends, sectors, briefingTitle, durationSeconds, executiveSummary)- Ground, render, and PUBLISH a Just Signal briefing to the public library. Grounds each ticker's live Day-0 price and computes exact dollar targets from your % projections. Targets MUST be percentages ("+18%") or multiples ("2.5x"), never dollars. assetOrSector: "Name (TICKER)" or "(PRIVATE)" for relative basis. Open to community contributions: the server itself renders every report, and tokenless publishing is rate-limited per day. Required: briefingTitle, executiveSummary, sectors, trends.
Last successful function declaration observed on . Source: https://www.ou-reports.com/api/mcp.php. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.ou-reports.com/api/mcp.php.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Package downloads | 70 downloads | Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. | 2026-07-30 to 2026-08-05 | npm | |
| Latest published version | 1.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-25 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-25 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.ou-reports.com | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | www.ou-reports.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json