MyScanity MCP server
de.myscanity/scannermyscanity.destreamable-httpv1.3.1Scanned
Ranked stock setups, trade plans, portfolio and watchlist for MyScanity users.
6 tools: 1 can delete or cancel things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No 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.
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 MyScanity MCP server can do
The MyScanity MCP server is published by myscanity.de, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: update_watchlist). 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.3.1.
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.
6 tools
Deletes or cancels 1Claude Code: deny
update_watchlistAdd, remove, or replace watchlist tickers (scope watchlist:write).No findings
Why it is in this group
- The name "update_watchlist" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
get_portfolioReturn the user's portfolio: pending, open, and closed positions with risk figures, compared with today's setups.No findings
Why it is in this group
- The name "get_portfolio" says "get": a word for reading.
Description, as the server wrote it Return the user's portfolio: pending, open, and closed positions with risk figures, compared with today's setups.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_trade_planReturn the trade plan for one ticker: entry, stop, 3R/5R targets, trailing hint, and instructions — or why there is no plan.No findings
Why it is in this group
- The name "get_trade_plan" says "get": a word for reading.
Description, as the server wrote it Return the trade plan for one ticker: entry, stop, 3R/5R targets, trailing hint, and instructions — or why there is no plan.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_watchlistReturn the custom watchlist of the active scanner profile (or ?profile_id=...).No findings
Why it is in this group
- The name "get_watchlist" says "get": a word for reading.
Description, as the server wrote it Return the custom watchlist of the active scanner profile (or ?profile_id=...).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_setupsReturn today's ranked stored setups with status and a compact trade plan or the reason it was skipped.No findings
Why it is in this group
- The name "list_setups" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whoamiReturn the token identity, its scopes, and the remaining rate-limit budget.No findings
Why it is in this group
- The name "whoami" says "whoami": a word for reading.
Description, as the server wrote it Return the token identity, its scopes, and the remaining rate-limit budget. Call this first to verify the connection. No arguments.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 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
- 1
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.myscanity.de/mcp: tools/list returned 6 tools to an anonymous client, including update_watchlist (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http scanner https://mcp.myscanity.de/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http scanner https://mcp.myscanity.de/mcp --header 'Authorization: <your-authorization>'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.
{
"permissions": {
"allow": [
"mcp__scanner__whoami",
"mcp__scanner__list_setups",
"mcp__scanner__get_trade_plan",
"mcp__scanner__get_portfolio",
"mcp__scanner__get_watchlist"
],
"ask": [],
"deny": [
"mcp__scanner__update_watchlist"
]
}
}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 scanner. Review it before you use it.
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/de.myscanity/scanner/verify?hash=4c238ee9be4f49a90fdc8ee614672098cf9bbc51bae89f96a768fccbb5d1cad9" | jq -e '.changed == false'Pinned hash 4c238ee9be4f, from Nov 16, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/de.myscanity/scanner/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/de.myscanity/scanner)Source: MCP Registry. Synced Nov 16, 2026, 17:17 UTC.
MyScanity MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MyScanity MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 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 MyScanity MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: update_watchlist.
Can the MyScanity 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 MyScanity MCP server have?
- 6 tools: 1 destructive, 5 read. update_watchlist, whoami, list_setups, get_trade_plan, get_portfolio and get_watchlist.
Does the MyScanity MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MyScanity MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MyScanity MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.