_ registry / mcp streamable-http

cubicle-copy

https://cubicle.algotrada.com

Registry code: aa5b40019b4547ee

api record

Cubicle copy-trading: The trading LLM models on the Taifoon venue with a verifiable record: which are live, their realized PnL, drawdown and win rate read from the venue's paired closes (models, model_record), and a quote for following one at the follower's own size inside the follower's own caps (follow_quote, max plan). Synthetic book actors are never listed. A record is past fills, never a forecast. Tools act as the caller's Cubicle principal; catalogue and plans answer without a key.

endpoint
https://cubicle.algotrada.com/deck/api/mcp/copy
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 6 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

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

  • catalogue unknown never probed

    The whole Cubicle API as data: the studio's eight-state machine and what each gate asks, every tool with the tier that opens it (and whether it is open to the caller), and the flows. Call it first when asked what Cubicle can do.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • account unknown never probed

    The caller's Cubicle account: their tier (free, Cubicle Operators holder, pro-50, max premium-99), their plan and until when, and every capability with whether it is open and which tier opens it. Call it before telling a trader what they can or cannot do.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • plans unknown never probed

    The Cubicle plans (price per 30 days, what each includes) and exactly how to pay on Robinhood Chain in USDG: the treasury, the token, and — when the subscription vault is live — the two wallet transactions (approve, subscribe) that renew automatically every 30 days. Nothing here moves money: the trader signs in their own wallet.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "plan": {
      "enum": [
        "pro-50",
        "premium-99"
      ],
      "type": "string",
      "description": "a plan id (pro-50 or premium-99) to prepare the payment steps for"
    },
    "wallet": {
      "type": "string",
      "description": "the 0x address of the wallet that will pay — needed for the renewing subscription, which is authorized for that wallet only"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • models unknown never probed

    The trading LLM models on the Taifoon venue a trader can study and, on the max plan, follow: each with its status (trading or stopped, derived from its last trade), markets, fills, realized PnL and win rate — all read from the venue, never from a model's words. Simulated market-maker and flow actors are never listed.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • model_record unknown never probed

    One trading model's record from the venue's first-in-first-out paired closes: realized PnL, maximum drawdown, win rate, per market, and the window. Always say what the record is not: a forecast, or what a follower would have made.

    mcp-tool

    {
  "type": "object",
  "required": [
    "model"
  ],
  "properties": {
    "model": {
      "type": "string",
      "description": "the model's attribution, from the models tool (starts with llm-)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • follow_quote unknown never probed

    Quote following a trading model (max plan): checks the model is live and followable, validates the follower's sizing (fixed_notional usd, or proportional bps of their balance) and caps (max_notional_usd, max_open_positions, max_daily_loss_usd, markets the model trades), and shows what one mirror would be at the given balance. Creates nothing and moves nothing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "model",
    "sizing",
    "caps"
  ],
  "properties": {
    "caps": {
      "type": "object",
      "description": "{\"max_notional_usd\":100,\"max_open_positions\":3,\"max_daily_loss_usd\":40,\"markets\":[\"BTC\"]}"
    },
    "model": {
      "type": "string",
      "description": "the model's attribution from the models tool"
    },
    "sizing": {
      "type": "object",
      "description": "{\"kind\":\"fixed_notional\",\"usd\":50} or {\"kind\":\"proportional\",\"bps\":200}"
    },
    "balance_usd": {
      "type": "number",
      "description": "the follower's balance, to show a mirror's size (optional)"
    }
  },
  "additionalProperties": false
}
    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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aa5b40019b4547ee/badge.svg)](https://brick.blue/agent/aa5b40019b4547ee)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

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.