# Social Security COLA 2027 MCP (remote · social-security-cola-2027-mcp.lipmichal.workers.dev)

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

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

## Components

- remote · `social-security-cola-2027-mcp.lipmichal.workers.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp)

## Channel facts

- Endpoint: `https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 927 tokens (~154/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**: 53/100
  - Stability observed for 16 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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Social Security COLA 2027 MCP server?

Social Security COLA 2027 MCP is a hosted endpoint at https://social-security-cola-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.

### Claude

```bash
claude mcp add --transport http theluckystrike-social-security-cola-2027-mcp 'https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-social-security-cola-2027-mcp": {
      "url": "https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-social-security-cola-2027-mcp": {
      "type": "http",
      "url": "https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-social-security-cola-2027-mcp]
url = "https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-social-security-cola-2027-mcp": {
      "type": "remote",
      "url": "https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-social-security-cola-2027-mcp --url 'https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-social-security-cola-2027-mcp:
    url: "https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-social-security-cola-2027-mcp": {
      "Transport": "http",
      "Url": "https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-social-security-cola-2027-mcp -t streamable-http -u 'https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-social-security-cola-2027-mcp": {
      "type": "http",
      "url": "https://social-security-cola-2027-mcp.lipmichal.workers.dev/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-20 (score 73, +1)

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

### 2026-11-18 (score 72, +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-11-16 (score 71, +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-11-13 (score 70, +1)

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

### 2026-11-11 (score 69, +1)

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

### 2026-11-09 (score 68, +1)

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

### 2026-11-07 (score 67, +1)

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

### 2026-11-06 (score 66, 0)

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

## MCP tools (6)

### `get_social_security_cola` (~157 tokens)

Get Social Security COLA

Social Security cost-of-living adjustment (COLA) for a payable year, from the SSA "Cost-of-Living Increase and Other Determinations" notice in the Federal Register. The 2027 COLA is 3.6 percent (effective December 2026, paid January 2027, published 2026-10-26). Also returns the COLA history back to 1996. Without a year it checks the Federal Register API for a newer notice.

Input parameters:

- `history_years` (integer): How many years of COLA history to include, newest first. Default 10.
- `year` (integer): Year the COLA is first paid (January). Default: the latest, 2027.

### `calculate_cola_increase` (~95 tokens)

Calculate COLA increase

Apply a year's Social Security COLA to a monthly benefit. Rounds down to the next lower 10 cents and shows the whole-dollar payment, as SSA does. Default year 2027 (3.6 percent).

Input parameters:

- `monthly_benefit` (number, required): Current monthly benefit in dollars, for example 2008.
- `year` (integer): Year the COLA is first paid. Default 2027.

### `get_full_retirement_age` (~111 tokens)

Get full retirement age

Full retirement age for Social Security from a birth date (20 CFR 404.409, including the January 1 rule and the day-before-birthday rule), the exact date and month it is reached, the earliest month benefits can start at 62 and the percent cut, the spouse percent at 62, delayed retirement credits to age 70 and the survivor full retirement age.

Input parameters:

- `birth_date` (string, required): Birth date as YYYY-MM-DD, for example "1960-07-15".

### `calculate_claiming_age_benefit` (~192 tokens)

Calculate benefit by claiming age

Monthly Social Security retirement benefit if claimed at a given age between 62 and 70, from the full-retirement-age amount (PIA). Uses 5/9 of 1 percent a month for the first 36 early months, 5/12 of 1 percent after that, and 2/3 of 1 percent a month of delayed credits for people born after 1942, with SSA dime rounding.

Input parameters:

- `birth_date` (string, required): Birth date as YYYY-MM-DD, for example "1960-07-15".
- `claim_age_months` (integer): Extra months, 0 to 11. Default 0.
- `claim_age_years` (integer, required): Claiming age in whole years, 62 to 70.
- `pia` (number, required): Monthly benefit at full retirement age (primary insurance amount) in dollars, from the SSA statement.

### `get_social_security_limits` (~101 tokens)

Get Social Security limits for a year

Social Security program amounts for 2023 to 2027 from the Federal Register notices: maximum taxable earnings (2027: $192,300), retirement earnings test limits (2027: $25,560 and $67,920), earnings per work credit, substantial gainful activity, trial work month, maximum federal SSI and PIA bend points.

Input parameters:

- `year` (integer): Year 2023 to 2027. Default 2027.

### `calculate_earnings_test` (~160 tokens)

Calculate earnings test withholding

How much Social Security withholds under the retirement earnings test for a year and annual earnings: $1 for every $2 over the limit, or $1 for every $3 in the year you reach full retirement age.

Input parameters:

- `annual_earnings` (number, required): Wages plus net self-employment earnings for the year, in dollars. In the year you reach full retirement age, only earnings before that month.
- `monthly_benefit` (number): Monthly benefit, to estimate how many months are withheld.
- `reaches_full_retirement_age_this_year` (boolean): True if you reach full retirement age during this year. Default false.
- `year` (integer): Year 2023 to 2027. Default 2027.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 68
- 2026-11-09: 68
- 2026-11-08: 67
- 2026-11-07: 67
- 2026-11-06: 66
- 2026-11-05: 66

## Common questions

### What is the Social Security COLA 2027 MCP server?

Social Security COLA 2027 MCP is listed in the public MCP registry as io.github.theluckystrike/social-security-cola-2027-mcp. Social Security COLA 2027, full retirement age, earnings test and 2027 limits from SSA notices. This page covers its hosted endpoint (https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp).

### Is the Social Security COLA 2027 MCP server safe to use?

Social Security COLA 2027 MCP 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 Social Security COLA 2027 MCP server expose?

Social Security COLA 2027 MCP exposes 6 tools: get_social_security_cola, calculate_cola_increase, get_full_retirement_age, calculate_claiming_age_benefit, get_social_security_limits, calculate_earnings_test. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.

### Does the Social Security COLA 2027 MCP server require authentication?

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

### Is the Social Security COLA 2027 MCP server still maintained?

Social Security COLA 2027 MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 Social Security COLA 2027 MCP server?

VerifyMCP ran 12 checks on Social Security COLA 2027 MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Social Security COLA 2027 MCP: HTTPS. 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://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/social-security-cola-2027-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-social-security-cola-2027-mcp/social-security-cola-2027-mcp
