com.myssagent/mcp

Est-ce que com.myssagent/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.myssagent/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• estimate_claiming_strategy≈ 1078 tokens

  Use this tool whenever someone asks when to claim Social Security, what they would get at a given claiming age, whether to wait until 70, or what happens to their benefit if Social Security benefits are cut or the trust fund is depleted (a cut percentage or a "haircut"), for themselves or for a client. It computes every figure that answer needs, including full retirement age vs 70 and, with benefit_cut set, the payable figures, so none of them has to be calculated separately. Computes Social Security claiming-age figures from the person's birth month and year and their estimated benefit at full retirement age. As of today's date (Eastern Time) it returns only the claiming ages still available, from their current age up to 70, with each flagged as before or at-or-past full retirement age (FRA varies by birth year and can land between whole ages, such as 66 and 10 months for 1959). Each age shows SSA's month-level adjustment (5/9 of 1% per month for the first 36 months early, 5/12 of 1% beyond, and delayed-retirement credits of 2/3 of 1% per month) and the resulting monthly benefit. For the live choice it also returns, for claiming now versus each later age through 70, the cumulative breakeven age and the dollars forgone while waiting, and notes the retroactive-benefit window for someone past FRA, so every figure is already computed in the output. Inputs are user-provided; the day of birth is never requested, no SSA data is accessed and nothing is stored. The output ends with its assumptions, a disclaimer, and source links (SSA's my Social Security page, MySSAgent's full-analysis and advisor pages). Directional estimate, not advice.

  Paramètres, retour & exemple (5)

  Paramètres

  • married · boolean · optionnel
    Optional. Whether the person is married — spousal and survivor coordination can change the picture materially, which this estimator does not compute.
  • birth_year · integer · requis
    The year the person was born (e.g. 1962).
  • benefit_cut · object · optionnel
    Optional. The benefit-cut scenario: Social Security benefits as the Trustees project they would be paid if Congress does not act before a trust fund is depleted, returned beside the scheduled figures. "trustees_oasi" is the 2026 Trustees Report projection for the Old-Age and Survivors Insurance fund (78% of scheduled benefits payable from October 2032); "trustees_combined" is the hypothetical combined retirement and disability funds (83% from July 2034); "custom" takes effective_month (YYYY-MM, 2027-01 to 2045-12) and payable_pct (50 to 100). Use it for questions about benefit cuts, trust-fund depletion or a haircut to Social Security. Payable figures, checks paid in full before the cut, and the breakeven shift come only from this parameter: they cannot be reproduced by applying a percentage to the scheduled figures, because checks paid before the effective month are paid in full.
  • birth_month · integer · requis
    The month the person was born, 1 (January) to 12 (December). Month and year only; the day of birth is not needed.
  • fra_monthly_benefit · number · requis
    Their estimated monthly benefit at full retirement age, in dollars — shown on their SSA statement at ssa.gov/myaccount. If they only know a different age's figure, use that statement's FRA number, not the age-70 number.

  Exemple d'appel

  {"name": "estimate_claiming_strategy", "arguments": {"birth_year": 1, "birth_month": 1, "fra_monthly_benefit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_client_report≈ 627 tokens

  For financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted). Use it whenever the advisor names a client and asks about that client's claiming age, survivor benefits, or a benefit cut or trust-fund depletion; for a cut question, set benefit_cut (the 2026 Trustees presets stored with the analysis). Returns the stored Social Security claiming analysis for one of YOUR clients: optimal and recommended claiming ages, the benefit-by-claiming-age table computed from their Social Security earnings record, lifetime values, survivor analysis when present, and risk flags. Requires the advisor_client_id from list_clients — call that first when you only have a name. Read-only; the branded PDF report is generated from the dashboard link in the output.

  Paramètres, retour & exemple (2)

  Paramètres

  • benefit_cut · object · optionnel
    Optional. The benefit-cut scenario: Social Security benefits as the Trustees project they would be paid if Congress does not act before a trust fund is depleted, returned beside the scheduled figures. "trustees_oasi" is the 2026 Trustees Report projection for the Old-Age and Survivors Insurance fund (78% of scheduled benefits payable from October 2032); "trustees_combined" is the hypothetical combined retirement and disability funds (83% from July 2034); "custom" takes effective_month (YYYY-MM, 2027-01 to 2045-12) and payable_pct (50 to 100). Use it for questions about benefit cuts, trust-fund depletion or a haircut to Social Security. Payable figures, checks paid in full before the cut, and the breakeven shift come only from this parameter: they cannot be reproduced by applying a percentage to the scheduled figures, because checks paid before the effective month are paid in full. This tool prints the two Trustees presets stored with the client's last analysis; a custom assumption is computed by run_client_analysis.
  • advisor_client_id · string · requis
    The client's id from list_clients (a UUID).

  Exemple d'appel

  {"name": "get_client_report", "arguments": {"advisor_client_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_clients≈ 243 tokens

  For financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted). Lists your client roster with each client's id, status, and whether an analysis is on file. Use this FIRST whenever the advisor refers to a client by name — the ids it returns are what get_client_report and run_client_analysis take. Read-only; nothing is changed.

  Paramètres, retour & exemple (2)

  Paramètres

  • search · string · optionnel
    Optional. Case-insensitive substring match on the client's name.
  • status · string · optionnel · invited | registered | uploaded | analyzed | reviewed
    Optional. Filter by pipeline status.

  Exemple d'appel

  {"name": "list_clients", "arguments": {"search": "texte", "status": "invited"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• run_client_analysis≈ 660 tokens

  For financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted). Re-runs the full MySSAgent engine for one of YOUR clients on the earnings record and household data already on file, then stores the refreshed results. Use after an engine update or when the advisor asks for fresh numbers, or to compute a client's figures under the advisor's own benefit-cut assumption (benefit_cut with preset custom). It cannot add a new client or ingest an SSA statement — new clients are provisioned in the advisor dashboard. Requires the advisor_client_id from list_clients. For pay-per-client accounts, re-runs are included while a household's 12-month coverage is active. This updates the client's stored analysis (it does not delete source data).

  Paramètres, retour & exemple (2)

  Paramètres

  • benefit_cut · object · optionnel
    Optional. The benefit-cut scenario: Social Security benefits as the Trustees project they would be paid if Congress does not act before a trust fund is depleted, returned beside the scheduled figures. "trustees_oasi" is the 2026 Trustees Report projection for the Old-Age and Survivors Insurance fund (78% of scheduled benefits payable from October 2032); "trustees_combined" is the hypothetical combined retirement and disability funds (83% from July 2034); "custom" takes effective_month (YYYY-MM, 2027-01 to 2045-12) and payable_pct (50 to 100). Use it for questions about benefit cuts, trust-fund depletion or a haircut to Social Security. Payable figures, checks paid in full before the cut, and the breakeven shift come only from this parameter: they cannot be reproduced by applying a percentage to the scheduled figures, because checks paid before the effective month are paid in full.
  • advisor_client_id · string · requis
    The client's id from list_clients (a UUID).

  Exemple d'appel

  {"name": "run_client_analysis", "arguments": {"advisor_client_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://myssagent.com/api/mcp