# MySSAgent Social Security Claiming Estimator (remote · myssagent.com)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `myssagent.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-myssagent-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-myssagent-mcp/api-mcp)

## Channel facts

- Endpoint: `https://myssagent.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (run_client_analysis).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2649 tokens (~441/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the MySSAgent Social Security Claiming Estimator MCP server?

MySSAgent Social Security Claiming Estimator is a hosted endpoint at https://myssagent.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-myssagent-mcp": {
      "url": "https://myssagent.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-myssagent-mcp": {
      "type": "http",
      "url": "https://myssagent.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-myssagent-mcp]
url = "https://myssagent.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-myssagent-mcp": {
      "type": "remote",
      "url": "https://myssagent.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-myssagent-mcp --url 'https://myssagent.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-myssagent-mcp:
    url: "https://myssagent.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-myssagent-mcp": {
      "Transport": "http",
      "Url": "https://myssagent.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-myssagent-mcp -t streamable-http -u 'https://myssagent.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-myssagent-mcp": {
      "type": "http",
      "url": "https://myssagent.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “run_client_analysis” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1954 → 2649
- [functional] New tool “get_sample_client_report”
- [functional] New tool “start_client_analysis”

### 2026-10-30 (score 70, +1)

- [security] Tool “get_client_report” rewrote its description, which is the text the model reads
- [cosmetic] “get_client_report” added an optional parameter “survivor_scenario”

### 2026-10-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `estimate_claiming_strategy` (~727 tokens)

Estimate Social Security benefit by claiming age

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.

Input parameters:

- `benefit_cut` (object): 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…
- `birth_month` (integer, required): The month the person was born, 1 (January) to 12 (December). Month and year only; the day of birth is not needed.
- `birth_year` (integer, required): The year the person was born (e.g. 1962).
- `fra_monthly_benefit` (number, required): 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, no…
- `married` (boolean): Optional. Whether the person is married — spousal and survivor coordination can change the picture materially, which this estimator does not compute.

### `get_sample_client_report` (~401 tokens)

See a sample client's claiming analysis

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.

Input parameters:

- `benefit_cut` (object): 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…
- `household` (string, required): Which sample household: married, widowed, divorced or single.

### `list_clients` (~118 tokens)

List your MySSAgent 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.

Input parameters:

- `search` (string): Optional. Case-insensitive substring match on the client's name.
- `status` (string): Optional. Filter by pipeline status.

### `get_client_report` (~562 tokens)

Get a client's claiming analysis

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.

Input parameters:

- `advisor_client_id` (string, required): The client's id from list_clients (a UUID).
- `benefit_cut` (object): 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…
- `survivor_scenario` (object): Married clients only. A scenario the ADVISOR models: which spouse passes first and at what age. It is a planning input, not a recommendation. The report then names the survivor and gives, for each pl…

### `run_client_analysis` (~397 tokens)

Re-run a client's claiming 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: 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).

Input parameters:

- `advisor_client_id` (string, required): The client's id from list_clients (a UUID).
- `benefit_cut` (object): 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…

### `start_client_analysis` (~231 tokens)

Start a new client's claiming analysis

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.

Input parameters:

- `client_name` (string, required): The client's name as the advisor gave it.
- `marital_status` (string, required): The client's marital status.
- `spouse_name` (string): Married clients only, optional: the spouse's name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-myssagent-mcp/api-mcp#diagnostics

## Score history

- 2026-11-06: 73
- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 66
- 2026-10-22: 66
- 2026-10-21: 65
- 2026-10-20: 65
- 2026-10-19: 66
- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64

## Common questions

### What is the MySSAgent Social Security Claiming Estimator MCP server?

MySSAgent Social Security Claiming Estimator is an MCP server listed in the public MCP registry as com.myssagent/mcp. Optimal Social Security claiming, in minutes. Benefit-by-age math from a deterministic engine. This page covers its hosted endpoint (https://myssagent.com/api/mcp).

### Is the MySSAgent Social Security Claiming Estimator MCP server safe to use?

MySSAgent Social Security Claiming Estimator scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MySSAgent Social Security Claiming Estimator MCP server expose?

MySSAgent Social Security Claiming Estimator exposes 6 tools: estimate_claiming_strategy, get_sample_client_report, list_clients, get_client_report, run_client_analysis, start_client_analysis. Their descriptions and schemas cost roughly 2,436 tokens of context every time the server is loaded.

### Does the MySSAgent Social Security Claiming Estimator MCP server require authentication?

No. We connected to MySSAgent Social Security Claiming Estimator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MySSAgent Social Security Claiming Estimator MCP server still maintained?

MySSAgent Social Security Claiming Estimator is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the MySSAgent Social Security Claiming Estimator MCP server?

VerifyMCP ran 13 checks on MySSAgent Social Security Claiming Estimator, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://myssagent.com/api/mcp
- Website: https://myssagent.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-myssagent-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-myssagent-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-myssagent-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-myssagent-mcp/api-mcp