Skip to content

MySSAgent Social Security Claiming Estimator MCP server

com.myssagent/mcpmyssagent.comstreamable-httpv2.0.0Scanned

Optimal Social Security claiming, in minutes. Benefit-by-age math from a deterministic engine.

6 tools: 1 can delete or cancel things, 2 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 2 write, 3 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.
Govern this server →

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 MySSAgent Social Security Claiming Estimator MCP server can do

The MySSAgent Social Security Claiming Estimator MCP server is published by myssagent.com, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: run_client_analysis) and create or change data (2 tools: estimate_claiming_strategy and start_client_analysis). 3 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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 2.0.0.

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
  • run_client_analysisFor financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted).No findings

    Why it is in this group

    • The name "run_client_analysis" says "run": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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: start_client_analysis starts a new client, and the statement is uploaded on myssagent.com. 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).

    Annotations the server declares

    • title: Re-run a client's claiming analysis
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • estimate_claiming_strategyUse 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Estimate Social Security benefit by claiming age
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • start_client_analysisFor financial advisors (sign in with your myssagent.com account when prompted; an advisor account is not needed yet).No findings

    Why it is in this group

    • The name "start_client_analysis" says "start": a word for a change.
    Description, as the server wrote it
    For financial advisors (sign in with your myssagent.com account when prompted; an advisor account is not needed yet). Use it when the advisor wants to add a new client or run MySSAgent's analysis for a client who is not on their roster yet. Takes only the client's name, marital status and, for a married client, the spouse's name, and returns one myssagent.com link where the advisor finishes: opening an advisor account if they have none, uploading the client's SSA statement (the birth dates and earnings record come from it), and running the analysis; a pay-per-client account pays for the household there, from its wallet. Nothing runs and nothing is charged in this conversation. Never pass a Social Security number, a birth date or an account number. After the advisor finishes on the page, list_clients and get_client_report return the new client here.

    Annotations the server declares

    • title: Start a new client's claiming analysis
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_client_reportFor financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted).No findings

    Why it is in this group

    • The name "get_client_report" says "get": a word for reading.
    Description, as the server wrote it
    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 (for a married client, the survivor benefit in both death orders, and with survivor_scenario a named survivor and an engine-computed survivor total), 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.

    Annotations the server declares

    • title: Get a client's claiming analysis
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_sample_client_reportUse this tool when a financial advisor wants to see what MySSAgent's advisor analysis looks like before they have an account, or asks for an example or sample client.No findings

    Why it is in this group

    • The name "get_sample_client_report" says "get": a word for reading.
    Description, as the server wrote it
    Use this tool when a financial advisor wants to see what MySSAgent's advisor analysis looks like before they have an account, or asks for an example or sample client. Needs no sign-in. Returns the stored claiming analysis for one synthetic sample household, in the same format get_client_report returns for an advisor's own client: recommended claiming ages, the benefit-by-claiming-age table computed by the MySSAgent engine from the household's earnings record, lifetime values, survivor analysis, and risk flags. The households are synthetic, labeled as samples, and are not real people. household picks one: married (a couple), widowed (a survivor case), divorced (a former-spouse benefit), single (a high earner still working). Read-only; nothing is stored.

    Annotations the server declares

    • title: See a sample client's claiming analysis
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_clientsFor financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted).No findings

    Why it is in this group

    • The name "list_clients" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List your MySSAgent clients
    • readOnlyHint: true
    • destructiveHint: false
    • 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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Nov 6, 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
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://myssagent.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://edjwxxefxuzdfwjnxjhb.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://myssagent.com/api/mcp: tools/list returned 6 tools to an anonymous client, including run_client_analysis (destructive), estimate_claiming_strategy (write), start_client_analysis (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

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.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  2. Tools2 added, 3 changed.+2 added~3 changedView diff

Install

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

claude mcp add --transport http myssagent https://myssagent.com/api/mcp
claude mcp add --transport http myssagent https://myssagent.com/api/mcp

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__myssagent__get_sample_client_report",
      "mcp__myssagent__list_clients",
      "mcp__myssagent__get_client_report"
    ],
    "ask": [
      "mcp__myssagent__estimate_claiming_strategy",
      "mcp__myssagent__start_client_analysis"
    ],
    "deny": [
      "mcp__myssagent__run_client_analysis"
    ]
  }
}

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 myssagent. 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/com.myssagent/mcp/verify?hash=95002b5507ab3cd19e791d64e75b767c58ff10e03a57a072923127fc22af200f" | jq -e '.changed == false'

Pinned hash 95002b5507ab, from Nov 13, 2026, 21:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.myssagent/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.myssagent/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.myssagent/mcp.svg)](https://radar.anlyon.com/servers/com.myssagent/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

MySSAgent Social Security Claiming Estimator MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MySSAgent Social Security Claiming Estimator MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 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 MySSAgent Social Security Claiming Estimator MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: run_client_analysis.

Can the MySSAgent Social Security Claiming Estimator 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 MySSAgent Social Security Claiming Estimator MCP server have?

6 tools: 1 destructive, 2 write, 3 read. run_client_analysis, estimate_claiming_strategy, start_client_analysis, get_sample_client_report, list_clients and get_client_report.

Does the MySSAgent Social Security Claiming Estimator MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MySSAgent Social Security Claiming Estimator MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MySSAgent Social Security Claiming Estimator MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.