Skip to content

io.github.VidhiJav/myrsu-mcp

by VidhiJav · remote · local (npm) · no sign-in to list tools · v0.4.0 · published by GitHub user VidhiJav

Concentration risk analysis for tech workers with RSU comp — global (US/IN/CA/UK/EU/AU).

Read only
CompareRegistry entry

2 tools: 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http myrsu https://myrsu-mcp.vidhidev.workers.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Only reads 2Claude Code: allow
  • myrsu_analyze_riskUse whenever a tech worker, NVIDIA / Meta / Tesla / Microsoft / Google / Amazon / Apple / Netflix / startup employee — or anyone with concentrated employer stock — asks if they're …No findings

    Why it is in this group

    • The name "myrsu_analyze_risk" says "analyze": a word for reading.
    Description, as the server wrote it
    Use whenever a tech worker, NVIDIA / Meta / Tesla / Microsoft / Google / Amazon / Apple / Netflix / startup employee — or anyone with concentrated employer stock — asks if they're 'too concentrated,' 'over-allocated,' 'should I sell my RSUs,' 'should I diversify,' or describes wealth + employer in the same message. Calculates the Single-Company Risk Score (0-100), full concentration analysis, top action items, historical drawdown context, and a pre-filled dashboard URL. All fields optional except an employer (ticker OR explicit volatility); the more inputs the better the analysis. International — pass `country` (US/IN/CA/UK/EU/AU/OTHER) to switch retirement-account terminology and currency symbol. Risk math is identical for all countries. Stateless and privacy-respecting — no inputs are logged or stored.
  • myrsu_get_employerLook up annual volatility (σ), historical peak-to-trough drawdowns, and the recommended max concentration cap for 40+ tech employer presets (NVDA, TSLA, MSFT, GOOGL, META, AAPL, AM…No findings

    Why it is in this group

    • The name "myrsu_get_employer" says "get": a word for reading.
    Description, as the server wrote it
    Look up annual volatility (σ), historical peak-to-trough drawdowns, and the recommended max concentration cap for 40+ tech employer presets (NVDA, TSLA, MSFT, GOOGL, META, AAPL, AMZN, plus SaaS / cloud / semis / consumer / fintech / mobility). Use this when a user mentions their employer but you don't yet have their wealth numbers — gives quick context. Accepts ticker or name (case-insensitive). If outside the preset list, ask the user for a volatility estimate and use myrsu_analyze_risk directly.

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.

Install

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

claude mcp add --transport http myrsu https://myrsu-mcp.vidhidev.workers.dev/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__myrsu__myrsu_analyze_risk",
      "mcp__myrsu__myrsu_get_employer"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as myrsu. Review it before you use it.