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

argos-technical

https://www.bullbear.ninja

Registry code: 9dbe6ca30f680039

api record

Use search + fetch for one stock, get_technical_analysis for up to 25 stocks, screen_technicals to filter the universe, and list_covered_stocks to browse coverage. Data is objective reference data, not investment advice.

endpoint
https://www.bullbear.ninja/api/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
_ is it live, free and safe measured by this hub
Is argos-technical live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is argos-technical free to use?
Yes — the hub reached it with no key and no payment.
What tools does argos-technical have?
5 tools: search, fetch, get_technical_analysis, list_covered_stocks, screen_technicals.
Is argos-technical 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
253ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 534 checks · signed record
  • down → live
  • unknown → live
_ what it is for
topic
finance & markets stock & market data
used for
  • get technical analysis for stocks
  • screen stocks by rsi and trend
  • search covered stocks
takes → gives
text, data → data
tools
5 reads
_ 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.

  • list_covered_stocks reads open 3h ago

    Browse the covered universe, optionally filtered by market, sector, or ticker/name. Results include the latest signal score and trend when available.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Default 50, max 200."
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1
    },
    "market": {
      "enum": [
        "us",
        "kr",
        "hk",
        "cn",
        "jp",
        "tw",
        "eu"
      ],
      "type": "string"
    },
    "sector": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1
    }
  }
}
    arguments 34 lines
  • screen_technicals reads open 3h ago

    Screen the covered universe by trend, signal score, RSI, market, and sector. Sort by 'below_high' or 'rsi_asc' for pullbacks/oversold stocks, or 'signal_desc'/'momentum_desc' for leaders.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "sort": {
      "enum": [
        "signal_desc",
        "signal_asc",
        "rsi_asc",
        "rsi_desc",
        "momentum_desc",
        "momentum_asc",
        "below_high",
        "near_high"
      ],
      "type": "string",
      "description": "Default 'signal_desc'."
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Default 50, max 200."
    },
    "trend": {
      "enum": [
        "bullish",
        "bearish",
        "mixed",
        "neutral"
      ],
      "type": "string"
    },
    "market": {
      "enum": [
        "us",
        "kr",
        "hk",
        "cn",
        "jp",
        "tw",
        "eu"
      ],
      "type": "string"
    },
    "sector": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1
    },
    "rsi_above": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
    },
    "rsi_below": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
    },
    "max_signal_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
    },
    "min_signal_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
    }
  }
}
    arguments 72 lines
  • search reads unknown 17h ago

    Search the covered stock universe by company name or ticker (KR/EN). Returns ids, titles, URLs, and short technical snippets. Pair with fetch for a full record.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Default 20, max 50."
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Company name or ticker substring (KR/EN)."
    }
  }
}
    arguments 21 lines
  • fetch reads unknown 17h ago

    Fetch the full technical record for one stock by id, ticker, or company name. Returns a readable summary and structured metadata.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Ticker or company name, e.g. '005930' or 'SK Hynix'."
    }
  }
}
    arguments 15 lines
  • get_technical_analysis reads unknown 3h ago

    Technical levels for one or more covered stocks (KR/US/HK/CN/JP/TW/EU) from the precomputed cache: price, MA5/20/60/120, RSI14, Bollinger position, support/resistance, 52-week range, momentum, volatility, trend, and a 0-100 signal score. Accepts tickers or Korean/English company names.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "tickers"
  ],
  "properties": {
    "tickers": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 25,
      "minItems": 1,
      "description": "Tickers or company names (KR/EN), up to 25."
    }
  }
}
    arguments 20 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 9dbe6ca30f680039.

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