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

adona-robot

https://api.adona-robot.com

Registry code: 6ef8fcfa8afa1ab0

api record

Adona Robot sells market data by capacity: one-second OHLC candles and a live bid/ask quote stream for FX pairs and spot metals, over REST and WebSocket, with redistribution allowed. Use get_offer for the plans and terms, list_symbols for what is available, and quote_price_for to price a usage. Data itself is read with an API key: get_candles here, with the key in the Authorization header (Bearer adk_live_...) or, where a gateway keeps Authorization for itself, in the X-API-Key header, and billed like GET /v1/candles, or the /v1 REST and WebSocket API (see the reference).

endpoint
https://api.adona-robot.com/mcp
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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
110ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 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.

  • list_symbols open 22h ago

    Every symbol a paid plan carries, with its name and class.

    mcp-tool

    {
  "type": "object",
  "title": "list_symbolsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_offer open 22h ago

    The data offer: plans, prices, limits, trial, continuous feed, links.

    mcp-tool

    {
  "type": "object",
  "title": "get_offerArguments",
  "properties": {}
}
    arguments 5 lines
  • get_candles unknown 22h ago

    Candle history for one symbol, one page, oldest first, with your API key in the request's Authorization header (Bearer adk_live_... or adk_test_...) or in its X-API-Key header (adk_live_..., for a client or gateway that keeps Authorization for itself; two different keys are refused with CONFLICTING_API_KEYS). Billed like GET /v1/candles: slices of 1000 bars, rounded up, an empty page costs nothing. timeframe is one of D1, H4, H1, M15, M5, M1, S1; limit 1 to 5000; page backwards with before = the previous answer's next_before. end_user_id names the person you serve, for the per-person minute ceiling. Refusals answer the /v1 codes.

    mcp-tool

    {
  "type": "object",
  "title": "get_candlesArguments",
  "required": [
    "symbol",
    "timeframe"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 50
    },
    "before": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Before",
      "default": null
    },
    "symbol": {
      "type": "string",
      "title": "Symbol"
    },
    "timeframe": {
      "type": "string",
      "title": "Timeframe"
    },
    "end_user_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "End User Id",
      "default": null
    }
  }
}
    arguments 47 lines
  • quote_price_for unknown never probed

    Price a month of usage: simultaneous connections at peak, slices of 1000 bars, and symbols followed live continuously. Answers the plan and the CHF total before VAT.

    mcp-tool

    {
  "type": "object",
  "title": "quote_price_forArguments",
  "required": [
    "simultaneous_connections",
    "slices_per_month"
  ],
  "properties": {
    "slices_per_month": {
      "type": "integer",
      "title": "Slices Per Month"
    },
    "continuous_symbols": {
      "type": "integer",
      "title": "Continuous Symbols",
      "default": 0
    },
    "simultaneous_connections": {
      "type": "integer",
      "title": "Simultaneous Connections"
    }
  }
}
    arguments 23 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 6ef8fcfa8afa1ab0.

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