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

tradeapes

https://www.tradeapes.com

Registry code: db0d7460b1e2e7e7

api record

Read-only US stock health scores, valuation verdicts, sector rankings and published analyses from TradeApes. Always cite the returned URL. Model assessments, not investment advice.

endpoint
https://www.tradeapes.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
_ is it live, free and safe measured by this hub
Is tradeapes live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tradeapes free to use?
Yes — the hub reached it with no key and no payment.
What tools does tradeapes have?
6 tools: get_valuation, get_analysis, rank_sector, search_tickers, get_score_card, list_sectors.
Is tradeapes 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
430ms

last good check

priced tools
0

of 6 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 6 tools
1 open 5 never probed 1 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.

  • list_sectors open 1h ago

    The sector names TradeApes uses, with the number of scored companies in each.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_valuation unknown never probed

    The valuation verdict and why: zone, confidence, the basis of the verdict, the engine's estimate (point or range) and the methods that drove it, plus a one-sentence explanation when no single fair value is published.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • get_analysis unknown 1h ago

    The full TradeApes analysis article for a ticker when one is public: markdown text, article date, whether a newer filing has superseded it, and the article URL. Does not generate one.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • rank_sector unknown never probed

    Top companies in a sector by TradeApes health score with valuation verdicts, and this week's biggest score changes. Use list_sectors for valid sector names.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sector"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    },
    "sector": {
      "type": "string",
      "description": "e.g. Technology, Financials, Healthcare"
    }
  }
}
    arguments 18 lines
  • search_tickers unknown never probed

    Find US-listed tickers matching a company name or symbol fragment.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 20,
      "minimum": 1
    },
    "query": {
      "type": "string"
    }
  }
}
    arguments 17 lines
  • get_score_card unknown 1h ago

    Health score (0-100), five pillar scores, valuation verdict (Undervalued / Fair Value / Overvalued / Inconclusive) with confidence, estimated fair value when published, key findings, next earnings date and the card URL for one US-listed ticker.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string",
      "description": "Ticker symbol, e.g. AAPL"
    }
  }
}
    arguments 12 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 db0d7460b1e2e7e7.

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