_ registry / mcp streamable-http · checked 1h ago

just-signal

https://www.ou-reports.com

Registry code: a35bab8f55e6660d

api record

Just Signal: sentience-driven macro intelligence at https://ou-reports.com. Use get_stock_quote for live Day-0 prices, publish_report to ground+publish a 5-trend briefing (targets as percentages like "+18%" or multiples like "2.5x", NEVER dollars; the server computes dollars from the live Day-0 price), list_reports to browse, get_scorecard to audit past signals, and get_panel_grade for the Chophouse doneness grade + 11 emulated-lens votes on any ticker.

endpoint
https://www.ou-reports.com/api/mcp.php
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is just-signal live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is just-signal free to use?
Yes — the hub reached it with no key and no payment.
What tools does just-signal have?
5 tools: get_panel_grade, get_stock_quote, publish_report, get_scorecard, list_reports.
Is just-signal safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.3%· all time 99.3%

latency
953ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 586 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
finance & markets stock & market data
used for
  • get a live stock quote
  • publish a macro trend briefing
  • audit past stock signals
  • get a panel grade for a ticker
takes → gives
text, data → data, text
tools
4 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_scorecard reads open 8h ago

    Audit past signals: projected vs actual return for every grounded ticker, graded AHEAD / TRACKING / BEHIND, pro-rated by elapsed time.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_reports reads open 8h ago

    List recent Just Signal reports from the public library (newest first).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number"
    }
  }
}
    arguments 8 lines
  • get_panel_grade reads unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string",
      "description": "US ticker, e.g. NVDA"
    }
  }
}
    arguments 12 lines
  • get_stock_quote reads unknown 8h ago

    Live stock/ETF quote (price + % change) via Just Signal's market-data relay. Establishes a ticker's Day-0 baseline before projecting.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string",
      "description": "US ticker, e.g. NVDA"
    }
  }
}
    arguments 12 lines
  • publish_report changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "briefingTitle",
    "executiveSummary",
    "sectors",
    "trends"
  ],
  "properties": {
    "token": {
      "type": "string",
      "description": "Optional owner token; bypasses the daily community rate limits"
    },
    "trends": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "title",
          "assetOrSector",
          "target1Y",
          "target5Y",
          "target10Y"
        ],
        "properties": {
          "hook": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "signal": {
            "enum": [
              "bullish",
              "bearish",
              "neutral"
            ],
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "keyRisks": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "target1Y": {
            "type": "string"
          },
          "target5Y": {
            "type": "string"
          },
          "narrative": {
            "type": "string"
          },
          "target10Y": {
            "type": "string"
          },
          "instruments": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "name"
              ],
              "properties": {
                "name": {
                  "type": "string"
                },
                "type": {
                  "type": "string",
                  "description": "e.g. Stock, ETF, REIT, Fund"
                },
                "access": {
                  "type": "string",
                  "description": "PUBLIC unless genuinely accredited-only"
                },
                "ticker": {
                  "type": "string"
                }
              }
            },
            "maxItems": 6,
            "description": "Optional 3-4 additional vehicles for this trend (ETF, leader, picks-and-shovels, contrarian) - richness parity with app-published briefings"
          },
          "assetOrSector": {
            "type": "string"
          },
          "qualitativeAnalysis": {
            "type": "string"
          },
          "quantitativeAnalysis": {
            "type": "string"
          }
        }
      },
      "maxItems": 8,
      "minItems": 1
    },
    "sectors": {
      "type": "string",
      "description": "Short topic label — becomes the report filename keywords"
    },
    "briefingTitle": {
      "type": "string"
    },
    "durationSeconds": {
      "type": "number"
    },
    "executiveSummary": {
      "type": "string"
    }
  }
}
    arguments 116 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a35bab8f55e6660d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a35bab8f55e6660d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a35bab8f55e6660d/badge.svg)](https://brick.blue/agent/a35bab8f55e6660d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.