Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+3 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. 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. 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
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +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.

  • 7 Nov 26 +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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://social-security-cola-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 social-security-cola-2027-mcp.lipmichal.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 6 exposed · ~816 tokens

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 →

Tool Tokens
calculate_claiming_age_benefit ~192

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.

NameTypeReqDescription
birth_datestringyesBirth date as YYYY-MM-DD, for example "1960-07-15".
claim_age_monthsinteger–Extra months, 0 to 11. Default 0.
claim_age_yearsintegeryesClaiming age in whole years, 62 to 70.
pianumberyesMonthly benefit at full retirement age (primary insurance amount) in dollars, from the SSA statement.

No output schema declared.

No examples provided.

calculate_cola_increase ~95

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).

NameTypeReqDescription
monthly_benefitnumberyesCurrent monthly benefit in dollars, for example 2008.
yearinteger–Year the COLA is first paid. Default 2027.

No output schema declared.

No examples provided.

calculate_earnings_test ~160

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.

NameTypeReqDescription
annual_earningsnumberyesWages plus net self-employment earnings for the year, in dollars. In the year you reach full retirement age, only earnings before that month.
monthly_benefitnumber–Monthly benefit, to estimate how many months are withheld.
reaches_full_retirement_age_this_yearboolean–True if you reach full retirement age during this year. Default false.
yearinteger–Year 2023 to 2027. Default 2027.

No output schema declared.

No examples provided.

get_full_retirement_age ~111

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.

NameTypeReqDescription
birth_datestringyesBirth date as YYYY-MM-DD, for example "1960-07-15".

No output schema declared.

No examples provided.

get_social_security_cola ~157

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.

NameTypeReqDescription
history_yearsinteger–How many years of COLA history to include, newest first. Default 10.
yearinteger–Year the COLA is first paid (January). Default: the latest, 2027.

No output schema declared.

No examples provided.

get_social_security_limits ~101

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.

NameTypeReqDescription
yearinteger–Year 2023 to 2027. Default 2027.

No output schema declared.

No examples provided.

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.

remote · social-security-cola-2027-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-social-security-cola-2027-mcp 'https://social-security-cola-2027-mcp.lipmichal.workers.dev/mcp'
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.