Retirement Contribution Limits 2027
REMOTE · RETIREMENT-CONTRIBUTION-LIMITS-2027-MCP.LIPMICHAL.WORKERS.DEV
401(k), IRA, HSA limits, age 60-63 catch-up, Roth catch-up rule, Social Security COLA, 2025-2027.
Available components
Last scanned (1 hour ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 963 tokens (~240/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://retirement-contribution-limits-2027-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebf145553d5751d20e0d3cd51e3d7a94 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of retirement-contribution-limits-2027-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://retirement-contribution-limits-2027-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://retirement-contribution-limits-2027-mcp.lipmichal.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_max_contribution Maximum contribution by age, year and plans ~372
Calculates the most a person can contribute for a year given age (on Dec. 31), plans held (401k, 403b, 457b, tsp, simple, ira, hsa_self, hsa_family) and optional wages. Applies the age 50+ catch-up, the SECURE 2.0 age 60-63 super catch-up (eligible only if age 60, 61, 62 or 63 at year end; 64 drops back), the HSA $1,000 catch-up at 55, the shared 402(g) limit across 401(k)/403(b)/TSP/SIMPLE, the separate 457(b) limit, and the compensation cap. With prior_year_fica_wages it tells whether catch-ups must be Roth under SECURE 2.0 section 603 (2026: over $150,000 of 2025 FICA wages).
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | yes | Age on December 31 of the year. |
| plan_offers_super_catch_up | boolean | – | False if the employer plan does not offer the age 60-63 catch-up. Default true. |
| plans | array | yes | Plans the person contributes to, e.g. ["401k","ira","hsa_family"]. |
| prior_year_fica_wages | number | – | Prior-year FICA wages (W-2 box 3) from the plan sponsor, for the Roth catch-up rule. |
| simple_higher_limits | boolean | – | True if the SIMPLE plan uses the higher small-employer limits. |
| wages | number | – | Compensation for the year in USD, used to cap deferrals and IRA contributions. |
| year | integer | yes | Calendar year: 2025, 2026 or 2027. |
No output schema declared.
No examples provided.
compare_years Compare limits between 2025, 2026 and 2027 ~133
Shows each retirement, IRA, HSA and Social Security figure for two years side by side with the dollar and percent change: 401(k) deferral, catch-ups, 415(c), compensation limit, HCE threshold, SIMPLE, IRA, Roth catch-up threshold, HSA, wage base, earnings test and COLA. Items the IRS has not yet published (2027 plan limits on 2026-11-02) come back as null, never estimated.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | integer | yes | Calendar year: 2025, 2026 or 2027. |
| to_year | – | yes | – |
No output schema declared.
No examples provided.
get_contribution_limits 401(k), IRA, HSA and SIMPLE contribution limits (2025-2027) ~316
Returns official IRS contribution limits for 2025, 2026 and 2027: 401(k)/403(b)/TSP and 457(b) elective deferral ($24,500 for 2026), age 50+ catch-up ($8,000 for 2026), the SECURE 2.0 age 60-63 super catch-up ($11,250), IRA limit and catch-up ($7,500 + $1,100 for 2026), SIMPLE limits, 415(c) total ($72,000), 401(a)(17) compensation limit, highly compensated employee threshold, Roth IRA phase-outs, HSA self/family limits (2027: $4,500 / $9,000, Rev. Proc. 2026-24) and the Social Security wage base (2027: $192,300). Also states the Roth catch-up rule status. Figures copied from IRS Notices 2024-80 and 2025-67 and the HSA Rev. Procs. 2027 plan and IRA limits were not yet announced on 2026-11-02 and the tool says so instead of guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which limits: all (default), 401k, 403b, 457b, tsp, simple, ira, roth_ira, hsa, 415c, hce, social_security. |
| year | integer | yes | Calendar year: 2025, 2026 or 2027. |
No output schema declared.
No examples provided.
get_social_security_cola Social Security COLA, wage base and earnings test ~142
Returns the Social Security cost-of-living adjustment and related figures from SSA's official annual notice in the Federal Register: 2027 COLA 3.6% (announced October 2026), 2027 taxable maximum (wage base) $192,300, retirement earnings test limits ($25,560 under full retirement age, $67,920 in the year you reach it, for 2027), quarter of coverage, SGA amounts and SSI federal payment. Covers 2025, 2026 and 2027.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | Calendar year: 2025, 2026 or 2027. |
No output schema declared.
No examples provided.
How do I install the Retirement Contribution Limits 2027 MCP server?
Retirement Contribution Limits 2027 is a hosted endpoint at https://retirement-contribution-limits-2027-mcp.lipmichal.workers.dev/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.
remote · retirement-contribution-limits-2027-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-retirement-contribution-limits-20 'https://retirement-contribution-limits-2027-mcp.lipmichal.workers.dev/mcp'
What is the Retirement Contribution Limits 2027 MCP server?
Retirement Contribution Limits 2027 is an MCP server listed in the public MCP registry as io.github.theluckystrike/retirement-contribution-limits-202…. 401(k), IRA, HSA limits, age 60-63 catch-up, Roth catch-up rule, Social Security COLA, 2025-2027. This page covers its hosted endpoint (https://retirement-contribution-limits-2027-mcp.lipmichal.workers.dev/mcp).
Is the Retirement Contribution Limits 2027 MCP server safe to use?
Retirement Contribution Limits 2027 scores 66 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 Retirement Contribution Limits 2027 MCP server expose?
Retirement Contribution Limits 2027 exposes 4 tools: get_contribution_limits, calculate_max_contribution, get_social_security_cola, compare_years. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.
Does the Retirement Contribution Limits 2027 MCP server require authentication?
No. We connected to Retirement Contribution Limits 2027 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Retirement Contribution Limits 2027 MCP server still maintained?
Retirement Contribution Limits 2027 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.