Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Optimal Social Security claiming, in minutes. Benefit-by-age math from a deterministic engine.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using MySSAgent Social Security Claiming Estimator
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http myssagent-social-security-claiming-estimator https://myssagent.com/api/mcpCapabilities
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.
DiscoveredFor 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.
DiscoveredUse 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.
DiscoveredFor 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.
DiscoveredFor 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).
DiscoveredFor 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 248 ms | 6 |