mcpbeat Sign in

MySSAgent Social Security Claiming Estimator MCP Server

by myssagent Your server? Claim it
not responding

MySSAgent Social Security Claiming Estimator is listed as active in the registry but did not answer our last check. It exposes 4 tools.

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

Uptime history 24 days of history · worst day 0%
24 days agonow
0.0%
Uptime 24h
0 of 91 checks
4
Tools
read from the server
88 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

25 Oct 3 tool descriptions were rewritten estimate_claiming_strategy, get_client_report, run_client_analysis
25 Oct 3 tools changed the parameters they ask for estimate_claiming_strategy, get_client_report, run_client_analysis
18 Oct a tool description was rewritten get_client_report

MySSAgent Social Security Claiming Estimator does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add mcp --transport http https://myssagent.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://myssagent.com/api/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://myssagent.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://myssagent.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://myssagent.com/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

client
get_client_report
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.
run_client_analysis
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).
clients
list_clients
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.
estimate
estimate_claiming_strategy
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.

Endpoints

URLTransportStateLatencyChecked
https://myssagent.com/api/mcp streamable-http answering 88 ms 14 min ago

Alternatives to MySSAgent Social Security Claiming Estimator

same job, measured the same way
AW-1 Sovereign Circuit Breaker
by mvikmanners

Deterministic sub-0.2ms AST security circuit breaker and agent containment engine.

5 tools answering
SPARDA
by zyx77550

AI writes. SPARDA proves. Deterministic, offline security gate for AI edits.

272 installs/wk local only
SPARDA
by zakariagharzouli

AI writes. SPARDA proves. Deterministic, offline security gate for AI edits.

local only
Social Security COLA 2027 MCP
by theluckystrike

Social Security COLA 2027, full retirement age, earnings test and 2027 limits from SSA notices.

6 tools answering
Suprawall MCP
by wiserautomation

SupraWall security gateway for AI agents. Provides deterministic guardrails for MCP agents.

29 installs/wk local only
ZeroDOM
by devhusnainai

The deterministic attack-surface perception layer for AI security agents

727 installs/wk local only
Python Code Validator
by jkanselaar

Validates AI-generated Python: syntax, lint, security scan and deterministic repair.

3 tools answering
Guardvibe
by goklab

Deterministic security layer your AI can't be. 649 rules, 39 tools, CLI + doctor + host audit.

1 225 installs/wk local only

MySSAgent Social Security Claiming Estimator — questions

Answers built from our own checks of this server.

What can MySSAgent Social Security Claiming Estimator do?
It exposes 4 tools, read directly from the server on our last check. Among them: estimate_claiming_strategy, get_client_report, list_clients, run_client_analysis. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is MySSAgent Social Security Claiming Estimator working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 88 ms. The bar chart above shows every period we have measured.
The registry lists MySSAgent Social Security Claiming Estimator as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect MySSAgent Social Security Claiming Estimator?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MySSAgent Social Security Claiming Estimator need an API key?
No. MySSAgent Social Security Claiming Estimator completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.