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

riskreward

https://riskreward.pro

Registry code: 6725b5b1ad066774

api record

RiskReward provides deterministic calculations from user-supplied inputs. Use tools only for their documented linear-instrument or historical-performance scope. Preserve units and disclose returned assumptions and warnings. Missing risk preferences or trade facts must be obtained from the user, not inferred. Results do not execute trades or access accounts.

endpoint
https://riskreward.pro/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 riskreward live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is riskreward free to use?
Yes — the hub reached it with no key and no payment.
What tools does riskreward have?
3 tools: calculate_net_risk_reward, calculate_position_size, analyze_trade_performance.
Is riskreward 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
290ms

last good check

priced tools
0

of 3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • calculate_net_risk_reward unknown 1h ago

    Compare gross and fee-adjusted reward-to-risk, loss and profit per unit, and breakeven win rate for a linear trade with known entry, stop and target. Accepts distinct entry/stop/target fee percentages. Use for questions about a planned R ratio or how fees change it. Direction is derived from entry and stop. Does not fetch venue fees or predict execution, liquidation, or trade outcomes.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "entryPrice",
        "stopPrice",
        "targetPrice"
      ],
      "properties": {
        "fees": {
          "type": "object",
          "required": [
            "entryPercent",
            "stopPercent"
          ],
          "properties": {
            "stopPercent": {
              "type": "number",
              "minimum": 0,
              "description": "Stop exit fee percent, e.g. 0.05.",
              "exclusiveMaximum": 100
            },
            "entryPercent": {
              "type": "number",
              "minimum": 0,
              "description": "Entry fee percent, e.g. 0.05 means 0.05%, not 5%.",
              "exclusiveMaximum": 100
            },
            "targetPercent": {
              "type": "number",
              "minimum": 0,
              "description": "Target exit fee percent; defaults to stopPercent.",
              "exclusiveMaximum": 100
            }
          },
          "description": "User-supplied rates. Omission explicitly assumes zero fees; no exchange rate lookup is performed.",
          "additionalProperties": false
        },
        "stopPrice": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Planned stop price. Direction is derived from entry and stop.",
          "exclusiveMinimum": 0
        },
        "entryPrice": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Planned entry price in quote currency per base unit.",
          "exclusiveMinimum": 0
        },
        "targetPrice": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Profit target price, opposite the stop relative to entry.",
          "exclusiveMinimum": 0
        },
        "quoteCurrency": {
          "type": "string",
          "pattern": "^[A-Z][A-Z0-9]{1,9}$",
          "description": "Currency shared by all monetary inputs. Defaults to USD; no currency conversion is performed."
        },
        "instrumentType": {
          "type": "string",
          "const": "linear",
          "description": "Linear quote-margined instruments only. Inverse contracts and liquidation are unsupported."
        }
      },
      "additionalProperties": false
    }
    arguments 69 lines
  • calculate_position_size unknown 1h ago

    Calculate position quantity and notional for a linear crypto futures trade from user-specified account balance, risk percentage, entry and stop. Includes separate entry/stop fees and optional target profit and net R. Direction is derived. Use when asked how much to buy or sell for a specified risk budget. Ask for missing prices or risk preference; do not invent them. Does not calculate liquidation, leverage, inverse contracts, exchange lot rounding, signals, or execute orders.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "entryPrice",
        "stopPrice",
        "accountBalance",
        "riskPercent"
      ],
      "properties": {
        "fees": {
          "type": "object",
          "required": [
            "entryPercent",
            "stopPercent"
          ],
          "properties": {
            "stopPercent": {
              "type": "number",
              "minimum": 0,
              "description": "Stop exit fee percent, e.g. 0.05.",
              "exclusiveMaximum": 100
            },
            "entryPercent": {
              "type": "number",
              "minimum": 0,
              "description": "Entry fee percent, e.g. 0.05 means 0.05%, not 5%.",
              "exclusiveMaximum": 100
            },
            "targetPercent": {
              "type": "number",
              "minimum": 0,
              "description": "Target exit fee percent; defaults to stopPercent.",
              "exclusiveMaximum": 100
            }
          },
          "description": "User-supplied rates. Omission explicitly assumes zero fees; no exchange rate lookup is performed.",
          "additionalProperties": false
        },
        "stopPrice": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Planned stop price. Direction is derived from entry and stop.",
          "exclusiveMinimum": 0
        },
        "entryPrice": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Planned entry price in quote currency per base unit.",
          "exclusiveMinimum": 0
        },
        "riskPercent": {
          "type": "number",
          "maximum": 100,
          "description": "User-chosen account risk percentage, e.g. 1 means 1%. Never infer a risk preference.",
          "exclusiveMinimum": 0
        },
        "targetPrice": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Optional profit target, opposite the stop relative to entry.",
          "exclusiveMinimum": 0
        },
        "quoteCurrency": {
          "type": "string",
          "pattern": "^[A-Z][A-Z0-9]{1,9}$",
          "description": "Currency shared by all monetary inputs. Defaults to USD; no currency conversion is performed."
        },
        "accountBalance": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Account balance in the same quote currency as prices.",
          "exclusiveMinimum": 0
        },
        "instrumentType": {
          "type": "string",
          "const": "linear",
          "description": "Linear quote-margined instruments only. Inverse contracts and liquidation are unsupported."
        }
      },
      "additionalProperties": false
    }
    arguments 82 lines
  • analyze_trade_performance unknown 1h ago

    Analyze up to 500 chronological closed trades supplied by the user, each with net P&L after costs and original risk. Returns win rate, profit factor, expectancy in currency and R, total net R, and optional closed-trade equity drawdown when initial equity is supplied. Use for reviewing an existing trade sample. No account access, deposits, intratrade drawdown, forecasts, signals, or new risk recommendations.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "trades"
      ],
      "properties": {
        "trades": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "netPnl",
              "initialRisk"
            ],
            "properties": {
              "netPnl": {
                "type": "number",
                "maximum": 1000000000000,
                "minimum": -1000000000000,
                "description": "Realized P&L after all fees and costs. Positive is profit; negative is loss."
              },
              "initialRisk": {
                "type": "number",
                "maximum": 1000000000000,
                "description": "Original planned risk amount, including planned fees if that is your convention. Do not replace it with a later stop risk.",
                "exclusiveMinimum": 0
              }
            },
            "additionalProperties": false
          },
          "maxItems": 500,
          "minItems": 1,
          "description": "Closed trades ordered chronologically, all using the same currency and risk convention. Maximum 500."
        },
        "initialEquity": {
          "type": "number",
          "maximum": 1000000000000,
          "description": "Starting equity before the ordered trades. Required only for equity drawdown metrics. No deposits or withdrawals are modeled.",
          "exclusiveMinimum": 0
        },
        "quoteCurrency": {
          "type": "string",
          "pattern": "^[A-Z][A-Z0-9]{1,9}$",
          "description": "Currency shared by all monetary inputs. Defaults to USD; no currency conversion is performed."
        }
      },
      "additionalProperties": false
    }
    arguments 49 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 6725b5b1ad066774.

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

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.