Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MyScanity

REMOTE · MCP.MYSCANITY.DE

Ranked stock setups, trade plans, portfolio and watchlist for MyScanity users.

Available components

+64 this week 68 Trust /100

Last scanned (16 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (16 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 800 tokens (~114/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

Changelog

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.

  • 21 Nov 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.

  • 19 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.

  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 663 → 800 ▼ functional
    • Schema quality: good → excellent functional
    • New tool “review_book” functional
  • 16 Nov 26 +4
    • Authorization: unverified → fail ▼ critical
    • Tool “update_watchlist” is now declared destructive security
    • Schema quality: 72 → 110 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • “get_trade_plan” reworded the description of “ticker” cosmetic
    • “get_watchlist” reworded the description of “profile_id” cosmetic
    • “list_setups” reworded the description of “setup_type” cosmetic
    • “list_setups” reworded the description of “status” cosmetic
    • “update_watchlist” reworded the description of “add” cosmetic
    • “update_watchlist” reworded the description of “idempotency_key” cosmetic
    • “update_watchlist” reworded the description of “profile_id” cosmetic
    • “update_watchlist” reworded the description of “remove” cosmetic
    • “update_watchlist” reworded the description of “replace” cosmetic
  • 15 Nov 26 +57
    • HSTS header: unverified → fail ▼ security
    • DNSSEC: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 14 Nov 26 4

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.myscanity.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.myscanity.de CN=YR1,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 RSA 4096 SHA256-RSA 63c6ed4aae971e9e686635b51320d5b8d7e
SANs: *.myscanity.de, myscanity.de
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 mcp.myscanity.de. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
myscanity.de. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.myscanity.de/mcp Verified 200
http (plaintext) http://mcp.myscanity.de/mcp HTTPS enforced 301 https://mcp.myscanity.de/mcp
MCP tools · 7 exposed · ~654 tokens

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 →

Tool Tokens
get_portfolio ~30

Return the user's portfolio: pending, open, and closed positions with risk figures, compared with today's setups.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_trade_plan ~71

Return the trade plan for one ticker: entry, stop, 3R/5R targets, trailing hint, and instructions — or why there is no plan.

NameTypeReqDescription
tickerstringyesTicker symbol as stored by the scan, e.g. NVDA or SAP.DE (max 20 characters).

Structured output declared, but exposes no named fields.

No examples provided.

get_watchlist ~43

Return the custom watchlist of the active scanner profile (or ?profile_id=...).

NameTypeReqDescription
profile_id––Scanner profile id; omit for the user's default profile.

Structured output declared, but exposes no named fields.

No examples provided.

list_setups ~179

Return today's ranked stored setups with status and a compact trade plan or the reason it was skipped. Optional filters: status (tradeable, no_plan, in_portfolio, pending, blacklisted) and setup_type. This is the scanning answer; do not fetch price bars.

NameTypeReqDescription
setup_type––Filter by setup type (exact match). Values include breakout, pullback, episodic_pivot, parabolic, supertrend, supertrend_sell, rs_leading, vcp, htf_momentum, cvi_rebound, cvi_sell, bollingerwilliam_l…
status––Filter by status: tradeable (a trade plan exists), no_plan (setup without a plan), in_portfolio (already held), pending (pending order), blacklisted (excluded ticker).

Structured output declared, but exposes no named fields.

No examples provided.

review_book ~124

Check a pasted book of holdings against today's industry rotation: for each position the matching industry group, its regime color (green/yellow/red), and sell/stale warnings, plus a rotation-stale flag. Free tool — works without a subscription. Nothing is stored; at most 50 positions.

NameTypeReqDescription
positionsarrayyesHoldings to review, each {ticker: str, weight_pct?: number 0–100}. Example: [{"ticker": "NVDA", "weight_pct": 12.5}]. At most 50 positions; tickers max 20 characters.

Structured output declared, but exposes no named fields.

No examples provided.

update_watchlist ~173

Add, remove, or replace watchlist tickers (scope watchlist:write). Pass add / remove / replace; replace cannot be combined with add/remove. Send the same Idempotency-Key when retrying.

NameTypeReqDescription
add––Ticker symbols to add; duplicates and tickers already on the list are ignored.
idempotency_key––Retry key (1–80 chars: A–Z a–z 0–9 . _ : + -). The same key and body within 24 h replays the stored response instead of writing twice.
profile_id––Scanner profile id; omit for the user's default profile.
remove––Ticker symbols to remove; symbols not on the list are ignored.
replace––Complete replacement list; cannot be combined with add or remove.

Structured output declared, but exposes no named fields.

No examples provided.

whoami ~34

Return the token identity, its scopes, and the remaining rate-limit budget. Call this first to verify the connection. No arguments.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the MyScanity MCP server?

MyScanity is a hosted endpoint at https://mcp.myscanity.de/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 · mcp.myscanity.de

# add to Claude Code
claude mcp add --transport http de-myscanity-scanner 'https://mcp.myscanity.de/mcp'
Common questions

What is the MyScanity MCP server?

MyScanity is an MCP server listed in the public MCP registry as de.myscanity/scanner. Ranked stock setups, trade plans, portfolio and watchlist for MyScanity users. This page covers its hosted endpoint (https://mcp.myscanity.de/mcp).

Is the MyScanity MCP server safe to use?

MyScanity scores 68 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 MyScanity MCP server expose?

MyScanity exposes 7 tools: whoami, list_setups, get_trade_plan, get_portfolio, review_book, and 2 more. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.

Does the MyScanity MCP server require authentication?

No. We connected to MyScanity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MyScanity MCP server still maintained?

MyScanity is still listed as active in the MCP registry. We last reached this channel on 21 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 MyScanity MCP server?

VerifyMCP ran 13 checks on MyScanity, 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.