TradeApes
REMOTE · WWW.TRADEAPES.COM
Stock health scores, valuation verdicts, sector rankings and analyses for 8,000+ US companies.
Available components
Last scanned (11 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 358 tokens (~59/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.tradeapes.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.tradeapes.com | CN=YR1,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | RSA 2048 | SHA256-RSA | 68e4cf48874c4c269036ee0a9c0cfad985a |
| SANs: www.tradeapes.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.tradeapes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tradeapes.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.tradeapes.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.tradeapes.com/mcp | HTTPS enforced | 301 | https://www.tradeapes.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_analysis Get the published AI-written analysis ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
get_score_card Get a stock's TradeApes score card ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. AAPL |
No output schema declared.
No examples provided.
get_valuation Get a stock's valuation detail ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
list_sectors List sectors ~26
The sector names TradeApes uses, with the number of scored companies in each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rank_sector Rank a sector by health score ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| sector | string | yes | e.g. Technology, Financials, Healthcare |
No output schema declared.
No examples provided.
search_tickers Search tickers by name or symbol ~36
Find US-listed tickers matching a company name or symbol fragment.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the TradeApes MCP server?
TradeApes is a hosted endpoint at https://www.tradeapes.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.tradeapes.com
claude mcp add --transport http com-tradeapes-tradeapes 'https://www.tradeapes.com/mcp'
What is the TradeApes MCP server?
TradeApes is an MCP server listed in the public MCP registry as com.tradeapes/tradeapes. Stock health scores, valuation verdicts, sector rankings and analyses for 8,000+ US companies. This page covers its hosted endpoint (https://www.tradeapes.com/mcp).
Is the TradeApes MCP server safe to use?
TradeApes scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TradeApes MCP server expose?
TradeApes exposes 6 tools: get_score_card, get_valuation, rank_sector, list_sectors, search_tickers, get_analysis. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.
Does the TradeApes MCP server require authentication?
No. We connected to TradeApes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TradeApes MCP server still maintained?
TradeApes is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TradeApes MCP server?
VerifyMCP ran 13 checks on TradeApes, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.