mcp server
myrsu-mcp
Concentration risk analysis for tech workers with RSU comp — global (US/IN/CA/UK/EU/AU).
Description as published by the maintainer. Source
- version 0.4.0
- active
active — Registry entry last updated 2026-05-18.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
myrsu_analyze_risk(cash, country, mortgage, cost_basis, home_value, other_debt, include_nii, other_assets, other_income, employer_type, state_tax_pct, student_loans, unvested_rsus, currency_symbol, employer_income, employer_ticker, credit_card_debt, federal_ltcg_pct, retirement_accounts, vested_company_stock, diversified_investments, employer_volatility_pct)- 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_employer(ticker_or_name)- 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. Required: ticker_or_name.
Last successful function declaration observed on . Source: https://myrsu-mcp.vidhidev.workers.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://myrsu-mcp.vidhidev.workers.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.4.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-18 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-18 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | myrsu-mcp.vidhidev.workers.dev | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | myrsu-mcp.vidhidev.workers.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json