# MyScanity (remote · mcp.myscanity.de)

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

- Trust score: 68/100 (medium)
- Change this week: +64
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-16). See the changelog below before you install this server.

## Components

- remote · `mcp.myscanity.de`: 68/100 (this document), [markdown](https://verifymcp.io/servers/de-myscanity-scanner/mcp.md), [page](https://verifymcp.io/servers/de-myscanity-scanner/mcp)

## Channel facts

- Endpoint: `https://mcp.myscanity.de/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_watchlist).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 800 tokens (~114/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http de-myscanity-scanner 'https://mcp.myscanity.de/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-myscanity-scanner": {
      "url": "https://mcp.myscanity.de/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-myscanity-scanner": {
      "type": "http",
      "url": "https://mcp.myscanity.de/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-myscanity-scanner]
url = "https://mcp.myscanity.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-myscanity-scanner": {
      "type": "remote",
      "url": "https://mcp.myscanity.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-myscanity-scanner --url 'https://mcp.myscanity.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-myscanity-scanner:
    url: "https://mcp.myscanity.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-myscanity-scanner": {
      "Transport": "http",
      "Url": "https://mcp.myscanity.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-myscanity-scanner -t streamable-http -u 'https://mcp.myscanity.de/mcp'
```

### Other

```json
{
  "mcpServers": {
    "de-myscanity-scanner": {
      "type": "http",
      "url": "https://mcp.myscanity.de/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 68, +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.

### 2026-11-19 (score 67, +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.

### 2026-11-17 (score 66, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 663 → 800
- [functional] Schema quality: good → excellent
- [functional] New tool “review_book”

### 2026-11-16 (score 65, +4)

- [critical regression] Authorization: unverified → fail
- [security] Tool “update_watchlist” is now declared destructive
- [functional regression] Schema quality: 72 → 110
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “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”

### 2026-11-15 (score 61, +57)

- [security regression] HSTS header: unverified → fail
- [security regression] DNSSEC: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] 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.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-11-14 (score 4)

First indexed and scored.

## MCP tools (7)

### `whoami` (~34 tokens)

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

### `list_setups` (~179 tokens)

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.

Input parameters:

- `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).

### `get_trade_plan` (~71 tokens)

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

Input parameters:

- `ticker` (string, required): Ticker symbol as stored by the scan, e.g. NVDA or SAP.DE (max 20 characters).

### `get_portfolio` (~30 tokens)

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

### `review_book` (~124 tokens)

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.

Input parameters:

- `positions` (array, required): Holdings 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.

### `get_watchlist` (~43 tokens)

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

Input parameters:

- `profile_id`: Scanner profile id; omit for the user's default profile.

### `update_watchlist` (~173 tokens)

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.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-myscanity-scanner/mcp#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 65
- 2026-11-15: 61
- 2026-11-14: 4

## 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.

## Links

- Remote endpoint: https://mcp.myscanity.de/mcp
- Authorisation metadata: https://mcp.myscanity.de/.well-known/oauth-protected-resource/mcp
- Website: https://www.myscanity.de/entwickler/api
- Changelog RSS feed: https://verifymcp.io/servers/de-myscanity-scanner/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-myscanity-scanner/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/de-myscanity-scanner/mcp.json
- HTML version of this page: https://verifymcp.io/servers/de-myscanity-scanner/mcp
