ai.quantifyme/quantifyme
REMOTE · MCP.QUANTIFYME.AI · SCANNED AUG 3
Describe a trading strategy in plain English and deploy a live signal model in one call. No signup.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (one_shot). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3550 tokens (~197/item across 18 items; 13 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.quantifyme.ai
claude mcp add --transport http ai-quantifyme-quantifyme https://mcp.quantifyme.ai/mcp
[mcp_servers.ai-quantifyme-quantifyme] url = "https://mcp.quantifyme.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-quantifyme-quantifyme": {
"type": "remote",
"url": "https://mcp.quantifyme.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-quantifyme-quantifyme --url https://mcp.quantifyme.ai/mcp --transport streamable-http
mcp_servers:
ai-quantifyme-quantifyme:
url: "https://mcp.quantifyme.ai/mcp" {
"mcpServers": {
"ai-quantifyme-quantifyme": {
"type": "http",
"url": "https://mcp.quantifyme.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 57
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 3 Aug 2026 · Probed https://mcp.quantifyme.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quantifyme.ai | CN=YE2,O=Let's Encrypt,C=US | 16 Jul 2026 | 14 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5da49df0e94ad7cca5d9edc960fa2852a0e |
| SANs: *.quantifyme.ai, quantifyme.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of mcp.quantifyme.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| quantifyme.ai. | absent | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.quantifyme.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.quantifyme.ai/mcp | HTTPS enforced | 301 | https://mcp.quantifyme.ai/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.
browse_community Browse Community Strategies (leaderboard) ~338
Browse the public community leaderboard of published strategies, ranked by a composite performance score (best first). No signup or key needed. Copy-trade flow: call this to find a top strategy, then pass its `id` to `one_shot` as `community_id` to deploy a live signal model running that exact strategy in one call. Args: limit: How many top entries to return (default 20, max 200). sort: Ranking metric, best-first — one of "composite" (default), "ret" (total return), "wr" (win rate), "sharpe", "n_trades". Mirrors the quantifyme.ai/community page's sortable columns, so an agent can pick the top strategy by the metric it cares about in one call. The sorted entries keep their `id`, so the winner is directly deployable via one_shot(community_id=...). Returns: dict with: - scripts (list[dict]): ranked entries, best first. Each has: id (int — pass to one_shot as community_id), username, title, description, created_at, score, and metrics {total_ret, sharpe_strat, win_rate, n_trades, mdd, profit_factor}. SHOW the top few with their win_rate / total_ret so the user can pick one. - count (int). - metric (str): the sort key applied.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| sort | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
find_strategy Find a Matching Strategy ~384
Find an existing PROVEN strategy that matches a plain-English idea, so you can offer the user a choice — deploy the existing one, or generate a fresh custom one. Mirrors the quantifyme.ai landing experience: "Found <X> by @<author> (WR/PF) — Use it / Generate fresh". CALL THIS FIRST when a user describes a strategy idea. Then present the match (if any) and ASK which they want: • Use it → one_shot(community_id=<match.community_id>) — deploys the exact proven strategy (free, no generation). • Generate fresh → one_shot(prompt="<their description>") — Claude writes a brand-new custom strategy for them. If there's no match, just offer to generate fresh. Args: description: the user's strategy idea in plain English (e.g. "buy EURUSD 15min when RSI < 30, sell when RSI > 70"). symbol: optional pair to constrain the match (EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD). timeframe: optional granularity to constrain the match (1min/5min/15min/1h). Returns: dict with: - match: the best existing strategy, or null. When present: {community_id, title, username, wr, pf, ret, n_trades, symbol, timeframe}. Pass community_id to one_shot to deploy it unchanged. - description: echoed back — pass as one_shot(prompt=...) to generate fresh. - suggestion: a ready-to-show sentence offering the user the choice.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | — |
| symbol | — | — | — |
| timeframe | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
generate_strategy Generate Strategy Code (no training) ~261
Generate Python strategy code (no training/deploy). Use when the user wants raw code. Args: features: NL description of features (e.g. "RSI 14, Bollinger Bands"). signals: NL description of signal logic (e.g. "Buy when RSI < 30"). model: ML model name (default Random Forest). risk: NL risk rules (e.g. "0.5% stop loss"). description: Optional one-line summary; treated as PRIMARY USER REQUEST. symbol: Currency pair the code should target. One of: EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD. Default EURUSD. timeframe: Candle granularity. One of: 1min, 5min, 15min, 1h. Default 15min. claude_model: "sonnet" (default) or "haiku" (faster, higher daily cap).
| Name | Type | Req | Description |
|---|---|---|---|
| claude_model | — | — | — |
| description | — | — | — |
| features | string | — | — |
| model | string | — | — |
| risk | string | — | — |
| signals | string | — | — |
| symbol | — | — | — |
| timeframe | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_deploy_result Get Deploy Result ~354
Wait for a `one_shot` deploy to finish and return its final result. `one_shot` returns a job_token immediately and the LIVE CARD already streams progress and renders the interactive backtest chart itself. Call this ONCE with the token to get the final numbers as TEXT so you can summarize them — it does NOT render another card (no need for get_model_chart). It BLOCKS until the deploy finishes (or ~2.5 min); on timeout it returns ok:false + pending:true — call it again with the same token. IMPORTANT: if `source == "community"`, the deploy used a PRE-EXISTING strategy by `@author` — tell the user that, share the `live_url` as the Live dashboard link, and ask whether they'd like to GENERATE A CUSTOM strategy instead. Use the `note` field as your guide. Args: job_token: the token returned by `one_shot`. Returns: dict with: ok, stem, model, live_url, symbol, timeframe, channels (list), stats:{ret, wr, pf, n, mdd} (out-of-sample test-split metrics — SHOW THESE), source ("community" | "generated"), author (community username if any), author_url + strategy_url (render @author and "pre-existing strategy" as those Markdown links), community_id, suggest_custom (bool), and note (a ready instruction — follow it). On failure: {ok:false, error} (or {pending:true}).
| Name | Type | Req | Description |
|---|---|---|---|
| job_token | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_model_chart Show Backtest Chart (equity + trades) ~252
Visualize a trained model's backtest — a cumulative-return chart + trade log + stats. Use after `one_shot` / `list_models` with the model's `stem` to SHOW the user how it traded (the "is it actually any good" view). In ChatGPT this renders an interactive widget. In Claude, render an interactive **artifact** from this tool's structured output: a line chart of the cumulative return plus a table of the trades. Args: stem: The model stem (e.g. "14_EURUSD_15min_Model_24") from `list_models` / `one_shot`. Returns: dict with: ok, stem, symbol, timeframe, stats {ret, wr, pf, n, mdd, sharpe}, and trades [{type, entry_time, exit_time, entry_price, exit_price, pnl, pnl_pct, exit_reason, period}] (most recent ~200). exit_reason is one of TP / SL / close_only / signal / end. ret/mdd/wr are fractions; pnl_pct is percent.
| Name | Type | Req | Description |
|---|---|---|---|
| stem | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_quote Get Current Price (G7 FX quote) ~183
Get the latest price for a G7 FX pair — a quick "what's it at now" check. Useful for context before deploying a strategy. The price is the close of the most recent 1-minute bar from the platform's market feed (not a raw live tick); FX markets close on weekends, so the `stale` flag marks a bar that is more than 15 minutes old. Args: symbol: G7 pair — one of EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD. Default EURUSD. Returns: dict with: symbol, price (latest close), time (bar timestamp, UTC), change + change_pct (vs the prior 1-min bar), stale (bool).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_strategy_code Get Community Strategy Code ~207
Get the actual Python code behind a community leaderboard strategy. Use after `browse_community`: pass an entry's `id` here to read its real `feature_engineering()` + `strategy_config()` source so the user can inspect or tweak it. To deploy it unchanged, pass the same id to `one_shot` as `community_id`. Read-only, no signup needed. Args: community_id: The `id` of a community entry (from `browse_community`). Returns: dict with: id, title, username, description, symbol, timeframe, metrics {total_ret, win_rate, profit_factor, n_trades, mdd, sharpe_strat}, and `code` (the full Python source). SHOW the code to the user, and offer to deploy it via one_shot(community_id=...) or tweak it first.
| Name | Type | Req | Description |
|---|---|---|---|
| community_id | integer | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
link_account Link My QuantifyMe Account ~168
Link this chat to the user's existing QuantifyMe account. Call this when the user says they already have a QuantifyMe account, or asks why their models are missing / where a model went, or wants what they deploy here to show up in their own dashboard. By default this connector works with NO signup: it mints an anonymous trial account per chat, so models deployed here belong to that throwaway identity rather than to the user's real one. This returns a short-lived URL; once the user opens it and approves, every later call in THIS chat acts as their account and deploys land in their own model list. Give the user the `link_url` to open. Nothing else is required from them.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_deployed List Deployed Live Models ~19
List the user's currently deployed (live) models.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_models List Trained Models ~21
List the user's trained models with pre-computed train/test stats.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
one_shot Deploy Strategy (generate + backtest + go live) ~700
End-to-end deploy: generate strategy → train → deploy live. One of `prompt` (free-form NL), `preset` (curated winning strategy), or `community_id` (copy a published community strategy) is required. If more than one is passed, precedence is community_id > preset > prompt. Args: prompt: Natural-language strategy description (e.g. "Buy when RSI < 30, sell > 70"). symbol: Currency pair to backtest on. One of: EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD. Default EURUSD. timeframe: Candle granularity. One of: 1min, 5min, 15min, 1h. Default 15min. claude_model: Which Claude variant to use for code generation. "sonnet" (default — best quality, 1/day free) or "haiku" (faster, 3/day free). Ignored when `preset` is set (no generation needed). preset: Curated winning-strategy slug. Skips Claude generation entirely — deploys a pre-saved strategy known to backtest well on the chosen symbol. Available slugs: ema_cross_fast, momentum, scalper_stack, sma_only, trend_ema, volatility, bb_squeeze, all_mix, pivot_kid_ema. Not every slug exists for every symbol — call list_models afterwards to confirm what deployed. community_id: Copy-trade a published community strategy. Pass the `id` of an entry from `browse_community`. Loads that exact strategy code, skips Claude generation, then trains + deploys it. `symbol`/`timeframe` still apply to the backtest+deploy. webhook_url: Optional webhook to receive live signals. telegram_chat_id: Optional Telegram chat ID for signal delivery. Returns IMMEDIATELY (the deploy runs in the background so the live card can stream progress) with: - job_token (str): pass to get_deploy_result to fetch the final result. - poll_url (str): the card polls this for live progress; you can ignore it. - pending (bool): always true here — the deploy is still running.…
| Name | Type | Req | Description |
|---|---|---|---|
| claude_model | — | — | — |
| community_id | — | — | — |
| preset | — | — | — |
| prompt | — | — | — |
| symbol | — | — | — |
| telegram_chat_id | — | — | — |
| timeframe | — | — | — |
| webhook_url | — | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
stream_test Live Streaming Diagnostic ~115
Diagnostic: test whether LIVE data streaming works in this client. Renders a widget with three panels — a JS timer (baseline), a WebSocket to the live price feed, and an HTTP poll of /quote — each showing a live value + status, so you can see exactly which streaming mechanisms the client's widget sandbox actually permits. Use when a live/ticking chart isn't moving. Args: symbol: G7 pair to stream (default EURUSD).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
top_up Top Up Credits with Crypto ~75
Fund your QuantifyMe credits with crypto (USDC) — no signup, no human, no card. The agent-native funding rail. SIMULATED in this build (no real charge) and capped at $100 for the POC. Returns your new credit balance.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.