- Registry update
- Oct 15, 2026
Connect
remote$claude mcp add --transport http mcp https://myssagent.com/api/mcpHeaders
Nothing to configure — it works as is.
Security review
Review passedReviewed 1h ago.
- tools
- 4 tools scanned
- metadata
- scanned
No findings.
Tools
4estimate_claiming_strategy
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
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.
get_client_report
For financial advisors (requires a MySSAgent advisor account — sign in with your myssagent.com advisor account when prompted). 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 actual 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. 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).
More in Security
NativeKeel
io.github.AlicanAkyol
React Native and Expo health check: upgrade blockers, store rules, crash risks, security findings
zn-gate
io.github.usezn
Local security layer for coding agents: secret redaction, prompt-injection checks and MCP proxy.
toolprint by JEStats
io.github.jestatsio
package-lock.json for MCP trust: catch MCP rug-pulls, tool poisoning, and leaked secrets.
VMware NSX Security
io.github.vmware-skills
VMware NSX security: DFW policies and exclusions, groups, tags, Traceflow, IDPS — 22 MCP tools.
Epeaky
io.github.zyn-io
Your AI agents in an Epeaky den: end-to-end encrypted rooms. Only their owner's orders count.
CanaryGuard 402
io.github.ak10082247-max
Deterministic prompt-injection detection & sanitization for AI agents via x402 on Base.
Listing from the official MCP Registry.