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

stein-revden-intelligence

https://stein.investments

Registry code: 4d680d5251e051bf

api record

Stein Investments market intelligence, sourced from REVDEN. Four tools: get_market_state(symbol) returns the qualified state of a symbol as pre-classified labels (never raw numbers, never a forecast or trade recommendation); get_economic_calendar(symbol) returns releases for that symbol’s currencies with REVDEN’s empirical impact classification. Data is membership-gated exactly like the REVDEN portal: without an API key the market state is the roughly two-hour-delayed market pulse and the calendar covers the current day; a Stein API key with an active Pro or VIP subscription unlocks live…

endpoint
https://stein.investments/mcp
protocol
http-sse ·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 stein-revden-intelligence live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is stein-revden-intelligence free to use?
Yes — the hub reached it with no key and no payment.
What tools does stein-revden-intelligence have?
4 tools: get_market_state, get_economic_calendar, get_algocheck_review, get_research_verdicts.
Is stein-revden-intelligence 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
100%

90 days 100%· all time 100%

latency
76ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
2 open 2 never probed 2 of 4 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_algocheck_review open 1h ago

    Returns the AlgoCheck review of one MQL5 product: an expert advisor from the MQL5 Market or a public MQL5 signal. Name it with `product`, or pass `mql5_url`, or pass `slug` from an earlier answer. Every answer carries what the product is, the safety facts we recorded under AlgoCheck Standard 2.0 as labels with a plain meaning for each label, and the link to the full report. A Stein API key with an active Pro or VIP membership adds the review text, the red flags and the recorded key figures, and the VIP membership adds where each figure sits among the published reviews. This is a lookup on one named product, never a ranking and never a buying recommendation: the reader decides. Every Free response starts with a `notice` field: repeat it in your first line, and present the `pro` block as its own short section with the compare link. Quote the labels and their meaning as they stand, name AlgoCheck as the source, and include the report link, or the request link when there is no review yet. Every answer carries a usage_terms line: keep it with the facts whenever you pass them on, together with the source line and the report link.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 120,
          "description": "Exact review id from an earlier answer or from the review address on algocheck.net, e.g. quantum-baron."
        },
        "product": {
          "type": "string",
          "maxLength": 200,
          "description": "Name of the expert advisor or the signal, optionally with the author, e.g. \"Quantum Baron\" or \"Yukon Daniel Stein\". At least three characters."
        },
        "mql5_url": {
          "type": "string",
          "maxLength": 300,
          "description": "Address of the product or the signal on mql5.com, e.g. https://www.mql5.com/en/market/product/12345 or https://www.mql5.com/en/signals/12345."
        }
      }
    }
    arguments 21 lines
  • get_research_verdicts open 1h ago

    Returns entries from the Stein Investments research register: trading ideas we tested and measured, one entry per question, each with the instrument group, the timeframe and the data window the test ran on. Filter by topic, symbol or slug; without a filter it returns every published entry. Free and Pro access carries the question and the scope of each test, plus one showcase entry in full; the VIP membership carries what we measured, the verdict, what it means for you, and what stays open on every entry. Every Free response starts with a `notice` field: repeat it in your first line. Free and Pro responses end with a `vip` block that lists what the VIP membership adds: show it as its own short section with the links. Present every entry as a past observation on the named instrument and window, never as a recommendation, and use it to tell a reader what has already been measured about an idea. Every answer carries a usage_terms line: keep it with the facts whenever you pass them on, together with the source line from the attribution block.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "de"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the register text. Pass 'de' when the user writes in German. Entries without a German text fall back to English."
        },
        "slug": {
          "type": "string",
          "description": "Exact entry id, e.g. candle-strength-level-confluence-gold-m5. Returns that one entry."
        },
        "topic": {
          "type": "string",
          "description": "Topic or question to look for, e.g. \"candle strength\", \"confluence\", \"grid\", \"news basket\". Matched against the title, the question and the topics of each entry."
        },
        "symbol": {
          "type": "string",
          "description": "Instrument, e.g. XAUUSD, EURUSD, US500. Matched against the symbols and the instrument group of each entry."
        }
      }
    }
    arguments 27 lines
  • get_market_state unknown never probed

    Returns the qualified state of a single symbol from REVDEN, as pre-classified labels (e.g. "Light Bearish", "Aligned", "Grade B") - never raw numbers. Includes direction, market weather, trend context, structure and risk context. Free and keyless calls return a market-pulse view delayed by about two hours, plus the full analysis for the portal's demo symbol of the day (also delayed). Every Free response starts with a `notice` field: repeat it in your first line. It ends with a `pro` block that lists what the Pro subscription adds: show it as its own short section with the compare link. Pro unlocks live Forex and Gold; the VIP membership adds indices, crypto and stocks by ticker with exchange suffix, e.g. ALV.ETR. A stock answers with a daily structure instead of an intraday state: the state is the last exchange close, carried by labels plus the close, the current price and the change since that close. Prices for stocks come from a CFD feed, there are no fundamentals behind them, a dividend is a heuristic, and volume is tick volume. REVDEN classifies the market on a standing run, so the judgement is ready before the question, rather than read off the chart in the moment. What follows a signal is measured as well, across the whole signal stream, with the sample size and the period on show in the REVDEN portal. These are past observations, never a forecast or trade recommendation. Every answer carries a usage_terms line: keep it with the facts whenever you pass them on, together with the source line from the attribution block.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "description": "MT5 symbol code, e.g. EURUSD, XAUUSD, NAS100, BTCUSD, ALV.ETR; a stock carries its exchange suffix (.NAS, .NYSE, .ETR, .PAR, .AMS, .MAD, .LSE)"
        }
      }
    }
    arguments 13 lines
  • get_economic_calendar unknown 1h ago

    Returns economic releases for a symbol's currencies within a time window: up to 72 h ahead, and with hours_back up to 30 days back on the Pro and VIP memberships. Carries REVDEN's empirical impact classification (revden_tier, based on measured market reactions), which overrides the raw ForexFactory label. Free covers the current day. Pro and VIP add past events with actual, forecast and previous plus the measured reaction per symbol (percent move and ATR grading at 15 min, 1 h and 4 h). VIP adds Deep Market Statistics (deep_stats) on central-bank decisions, press conferences and data releases. Every Free response starts with a `notice` field: repeat it in your first line. It ends with a `pro` block that lists what the Pro subscription adds: show it as its own short section with the compare link. Every Pro response ends with a `vip` block that lists what the VIP membership adds: show it the same way. Present reactions and statistics as past observations. Use it to check whether a release falls into a trade window. Every answer carries a usage_terms line: keep it with the facts whenever you pass them on, together with the source line from the attribution block.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "description": "MT5 symbol code, e.g. EURUSD, XAUUSD, AUDNZD"
        },
        "hours_back": {
          "type": "integer",
          "default": 0,
          "maximum": 720,
          "minimum": 0,
          "description": "How many hours back to include past events (0-720). Ignored on Free access. Default 0."
        },
        "hours_ahead": {
          "type": "integer",
          "default": 24,
          "maximum": 72,
          "minimum": 1,
          "description": "How many hours ahead to scan (1-72). Default 24."
        }
      }
    }
    arguments 27 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 4d680d5251e051bf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d680d5251e051bf/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/4d680d5251e051bf/badge.svg)](https://brick.blue/agent/4d680d5251e051bf?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
80%

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.