Skip to content

quantifyme MCP server

ai.quantifyme/quantifymequantifyme.aistreamable-httpv1.0.0Scanned

Describe a trading strategy in plain English and deploy a live signal model in one call. No signup.

13 tools: 1 can delete or cancel things, 4 change things and 8 only read.

Tools: 1 delete, 0 irreversible, 4 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 13
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the quantifyme MCP server can do

The quantifyme MCP server is published by quantifyme.ai, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (1 tool: one_shot) and create or change data (4 tools: link_account, top_up, generate_strategy and stream_test). 8 tools only read.

13 tools bring in text other people can write (one_shot, get_deploy_result, link_account and 10 more).

The fixed checks matched 3 findings (long-description, annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Deletes or cancels 1Claude Code: deny
  • one_shotEnd-to-end deploy: generate strategy → train → deploy live.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,943 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...he result carries a `suggestion`, you may offer that community strategy."

      What this check looks for
    Description, as the server wrote it
    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. - symbol, timeframe (str). Call this EXACTLY ONCE per request. Pass the user's words as `prompt`; do not pre-pick presets/community strategies - the server routes (vague → the best curated preset for the market, or a fresh build when there is none; specific rules → a fresh generation). A community strategy deploys only after the user has seen its author and code (get_strategy_code) and picked it: then pass its `community_id`. NEXT STEP (always): call get_deploy_result(job_token) ONCE — it blocks until the deploy finishes and returns the out-of-sample stats + `stem` + `source`/`author` as TEXT so you can summarize. The live card already shows the chart, so you do NOT need get_model_chart. If source='community', tell the user it used a pre-existing strategy by @author and offer to generate a custom one. If the result carries a `suggestion`, you may offer that community strategy.

    Annotations the server declares

    • title: Deploy Strategy (generate + backtest + go live)
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Changes things 4Claude Code: ask
  • generate_strategyGenerate Python strategy code (no training/deploy).Reads text others writeNo findings

    Why it is in this group

    • The name "generate_strategy" says "generate": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Generate Strategy Code (no training)
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • stream_testDiagnostic: test whether LIVE data streaming works in this client.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...panel (not offered: the feed needs a credential and none is sent to a widget), and..."

      What this check looks for
    Description, as the server wrote it
    Diagnostic: test whether LIVE data streaming works in this client. Renders a widget with three panels: a JS timer (baseline), the WebSocket panel (not offered: the feed needs a credential and none is sent to a widget), and an HTTP poll of /quote, each showing a live value + status, so you can see which streaming mechanisms the client's widget sandbox permits. Use when a live/ticking chart isn't moving. Args: symbol: G7 pair to stream (default EURUSD).

    Annotations the server declares

    • title: Live Streaming Diagnostic
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • top_upSimulated crypto top-up for a QuantifyMe DEV server only: no money moves, so it never makes an account paid and grants at most up to the free credit cap ($100 per call).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Simulated crypto top-up for a QuantifyMe DEV server only: no money moves, so it never makes an account paid and grants at most up to the free credit cap ($100 per call). quantifyme.ai refuses it (#1098) and answers with how to pay for real: send USDC on Base to your deposit address (GET /api/v1/wallet/deposit_address). Returns your new credit balance.

    Annotations the server declares

    • title: Top Up Credits with Crypto
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 8Show 8 read-only tools
  • browse_communityBrowse the public community leaderboard of published strategies, ranked by a composite performance score (best first).Reads text others writeNo findings

    Why it is in this group

    • The name "browse_community" says "browse": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "browse_community" says "browse": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Browse Community Strategies (leaderboard)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • find_strategyFind 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.Reads text others writeNo findings

    Why it is in this group

    • The name "find_strategy" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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". Use this when a user wants to browse for an existing strategy. A vague deploy request does NOT need it: one_shot(prompt=...) deploys the best curated preset or a fresh build. A community strategy is another user's code, so it deploys only after the user has seen its author and code (get_strategy_code with the match's community_id) and picked it. Present the match (if any) and ASK: • Use it → one_shot(community_id=<match.community_id>) — deploys the exact strategy they picked (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.

    Annotations the server declares

    • title: Find a Matching Strategy
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_deploy_resultWait for a `one_shot` deploy to finish and return its final result.Reads text others writeNo findings

    Why it is in this group

    • The name "get_deploy_result" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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` (the user picked it) - 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. A `suggestion` is a community strategy that matched a vague request; it was NOT deployed; offer it, and deploy it only after the user sees its author and code and picks it. 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 ("preset" | "generated" | "community"), author (community username if any), author_url + strategy_url (render @author and "pre-existing strategy" as those Markdown links), community_id, suggest_custom (bool), suggestion ({community_id, title, author} or null: offered, not deployed), and note (a ready instruction - follow it). On failure: {ok:false, error} (or {pending:true}).

    Annotations the server declares

    • title: Get Deploy Result
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_model_chartVisualize a trained model's backtest — a cumulative-return chart + trade log + stats.Reads text others writeNo findings

    Why it is in this group

    • The name "get_model_chart" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Show Backtest Chart (equity + trades)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_quoteGet the latest price for a G7 FX pair — a quick "what's it at now" check.Reads text others writeNo findings

    Why it is in this group

    • The name "get_quote" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get Current Price (G7 FX quote)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_strategy_codeGet the actual Python code behind a community leaderboard strategy.Reads text others writeNo findings

    Why it is in this group

    • The name "get_strategy_code" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Community Strategy Code
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • list_deployedList the user's currently deployed (live) models.Reads text others writeNo findings

    Why it is in this group

    • The name "list_deployed" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the user's currently deployed (live) models.

    Annotations the server declares

    • title: List Deployed Live Models
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • list_modelsList the user's trained models with pre-computed train/test stats.Reads text others writeNo findings

    Why it is in this group

    • The name "list_models" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the user's trained models with pre-computed train/test stats. `acting_as` names the identity listed: the linked account or a trial user (#1962).

    Annotations the server declares

    • title: List Trained Models
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write13
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.quantifyme.ai/mcp: tools/list returned 11 tools to an anonymous client, including one_shot (destructive), link_account (write), generate_strategy (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • RFC 9728 protected resource metadata: https://mcp.quantifyme.ai/.well-known/oauth-protected-resource to none
    • Authorization servers: https://mcp.quantifyme.ai to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 5 to 3

Findings

Matches of fixed checks, with the text they matched.

1 warn2 info
  • The server marks "link_account" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The name "link_account" says "link": a word for a change.

    What this check looks for
  • The description is 2,943 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...he result carries a `suggestion`, you may offer that community strategy."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...panel (not offered: the feed needs a credential and none is sent to a widget), and..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.quantifyme.ai/.well-known/oauth-protected-resource -> none; Authorization servers: https://mcp.quantifyme.ai -> none; Dynamic client registration: yes -> not observed…View diff
    • RFC 9728 protected resource metadata: https://mcp.quantifyme.ai/.well-known/oauth-protected-resource to none
    • Authorization servers: https://mcp.quantifyme.ai to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 3.View diff
    • Tools that change things, listed without credentials: 5 to 3

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http quantifyme https://mcp.quantifyme.ai/mcp
claude mcp add --transport http quantifyme https://mcp.quantifyme.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__quantifyme__get_deploy_result",
      "mcp__quantifyme__list_models",
      "mcp__quantifyme__list_deployed",
      "mcp__quantifyme__browse_community",
      "mcp__quantifyme__find_strategy",
      "mcp__quantifyme__get_strategy_code",
      "mcp__quantifyme__get_quote",
      "mcp__quantifyme__get_model_chart"
    ],
    "ask": [
      "mcp__quantifyme__link_account",
      "mcp__quantifyme__top_up",
      "mcp__quantifyme__generate_strategy",
      "mcp__quantifyme__stream_test"
    ],
    "deny": [
      "mcp__quantifyme__one_shot"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as quantifyme. Review it before you use it.

Capability tags behind 13 rules
  • mcp__quantifyme__one_shot untrusted-input
  • mcp__quantifyme__get_deploy_result untrusted-input
  • mcp__quantifyme__link_account untrusted-input
  • mcp__quantifyme__list_models untrusted-input
  • mcp__quantifyme__list_deployed untrusted-input
  • mcp__quantifyme__top_up untrusted-input
  • mcp__quantifyme__generate_strategy untrusted-input
  • mcp__quantifyme__browse_community untrusted-input
  • mcp__quantifyme__find_strategy untrusted-input
  • mcp__quantifyme__get_strategy_code untrusted-input
  • mcp__quantifyme__get_quote untrusted-input
  • mcp__quantifyme__get_model_chart untrusted-input
  • mcp__quantifyme__stream_test untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.quantifyme/quantifyme/verify?hash=5bf3340342159e97c534c95a28c832f73abfe20437fd344fee0ddf39d0cb9a60" | jq -e '.changed == false'

Pinned hash 5bf334034215, from Nov 11, 2026, 21:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.quantifyme/quantifyme/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.quantifyme/quantifyme
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.quantifyme/quantifyme.svg)](https://radar.anlyon.com/servers/ai.quantifyme/quantifyme)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

quantifyme MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the quantifyme MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the quantifyme MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: one_shot.

Can the quantifyme MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the quantifyme MCP server have?

13 tools: 1 destructive, 4 write, 8 read. one_shot, link_account, top_up, generate_strategy, stream_test, get_deploy_result, list_models, list_deployed and 5 more.

Does the quantifyme MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the quantifyme MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the quantifyme MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.