COLA Insight MCP server
io.github.ge3m0r/cola-insightge3m0rstreamable-httpv1.0.1Scanned
Read-only Social Security COLA data, calculations, history, and official source links.
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the COLA Insight MCP server can do
The COLA Insight MCP server is published by the GitHub account ge3m0r. It has 5 tools. It can create or change data (1 tool: calculate_benefit_change), but cannot delete data. 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
calculate_benefit_changeEstimate the monthly and annual benefit change using COLA Insight's latest tracked rate.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Estimate the monthly and annual benefit change using COLA Insight's latest tracked rate. This is an educational estimate, not an SSA benefit determination.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
calculate_retirement_claiming_estimateCompare claiming at ages 62 through 70 using birth-year-specific full retirement age and versioned current-law adjustment rules.No findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
Description, as the server wrote it Compare claiming at ages 62 through 70 using birth-year-specific full retirement age and versioned current-law adjustment rules. A monthly FRA benefit is optional; without it, the tool returns percentages only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_cola_historyReturn preserved forecast, formula-derived, and official COLA snapshots in reverse chronological order.No findings
Why it is in this group
- The name "get_cola_history" says "get": a word for reading.
Description, as the server wrote it Return preserved forecast, formula-derived, and official COLA snapshots in reverse chronological order.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_cola_sourcesReturn the government sources, methodology, data dictionary, and public datasets used by COLA Insight.No findings
Why it is in this group
- The name "get_cola_sources" says "get": a word for reading.
Description, as the server wrote it Return the government sources, methodology, data dictionary, and public datasets used by COLA Insight.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_current_colaReturn the latest tracked 2027 Social Security COLA status, rate, CPI-W observations, timestamp, and primary source links.No findings
Why it is in this group
- The name "get_current_cola" says "get": a word for reading.
Description, as the server wrote it Return the latest tracked 2027 Social Security COLA status, rate, CPI-W observations, timestamp, and primary source links.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.colainsight.com/mcp: tools/list returned 5 tools to an anonymous client, including calculate_benefit_change (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:calculate_retirement_claiming_estimateOnly reads
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http cola-insight https://www.colainsight.com/mcpclaude mcp add --transport http cola-insight https://www.colainsight.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cola-insight__get_current_cola",
"mcp__cola-insight__calculate_retirement_claiming_estimate",
"mcp__cola-insight__get_cola_history",
"mcp__cola-insight__get_cola_sources"
],
"ask": [
"mcp__cola-insight__calculate_benefit_change"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cola-insight. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ge3m0r/cola-insight/verify?hash=bcc7ea73c7f94057517c89ec56e39da05ab90dd1ec2ca912bc616a868ce4e481" | jq -e '.changed == false'Pinned hash bcc7ea73c7f9, from Nov 19, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ge3m0r/cola-insight/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ge3m0r/cola-insight)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.
COLA Insight MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the COLA Insight MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the COLA Insight MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the COLA Insight MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the COLA Insight MCP server have?
- 5 tools: 1 write, 4 read. calculate_benefit_change, get_current_cola, calculate_retirement_claiming_estimate, get_cola_history and get_cola_sources.
Does the COLA Insight MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the COLA Insight MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the COLA Insight MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.