api-changelog-tracker MCP server
io.github.lazymac2x/api-changelog-trackerlazymac2xstreamable-httpv1.0.0Scanned
Cloudflare Workers MCP server: api-changelog-tracker
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the api-changelog-tracker MCP server can do
The api-changelog-tracker MCP server is published by the GitHub account lazymac2x. It has 6 tools. It can create or change data (2 tools: detect_breaking_changes and subscribe_feed), but cannot delete data. 4 tools only read.
1 tool can send data out of your system (subscribe_feed).
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.
Last scanned Nov 21, 2026, version 1.0.0.
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.
6 tools
Changes things 2Claude Code: ask
detect_breaking_changesDetect breaking changes across one or multiple APIs.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.
Description, as the server wrote it Detect breaking changes across one or multiple APIs. Filter by severity (critical, high, medium, low) and date. Omit api_id to scan all APIs.
subscribe_feedRegister a webhook or email to receive changelog update notifications.Can send data outNo findings
Why it is in this group
- The name "subscribe_feed" says "subscribe": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Register a webhook or email to receive changelog update notifications. Returns a subscription ID.
Only reads 4Show 4 read-only tools
diff_versionsCompare changelog state between two dates for an API.No findings
Why it is in this group
- The name "diff_versions" says "diff": a word for reading.
Description, as the server wrote it Compare changelog state between two dates for an API. Shows what was added or removed in the range.
fetch_changelogFetch versioned changelog entries for a specific API (openai, anthropic, stripe, github, twilio, cloudflare, sendgrid, slack).No findings
Why it is in this group
- The name "fetch_changelog" says "fetch": a word for reading.
Description, as the server wrote it Fetch versioned changelog entries for a specific API (openai, anthropic, stripe, github, twilio, cloudflare, sendgrid, slack). Filter by date and breaking-only.
list_tracked_apisList all tracked APIs with metadata and latest changelog status.No findings
Why it is in this group
- The name "list_tracked_apis" says "list": a word for reading.
Description, as the server wrote it List all tracked APIs with metadata and latest changelog status. Filter by category (ai, payments, developer-tools, communications, infrastructure, email).
searchFull-text search across all changelog entries.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Full-text search across all changelog entries. Searches title, summary, and change descriptions.
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.
- 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 out1
- 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:29 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
- 2
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.lazy-mac.com/.well-known/oauth-protected-resource/api-changelog-tracker/mcp
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lazy-mac.com/api-changelog-tracker/mcp: tools/list returned 6 tools to an anonymous client, including detect_breaking_changes (write), subscribe_feed (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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http api-changelog-tracker https://api.lazy-mac.com/api-changelog-tracker/mcpclaude mcp add --transport http api-changelog-tracker https://api.lazy-mac.com/api-changelog-tracker/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__api-changelog-tracker__list_tracked_apis",
"mcp__api-changelog-tracker__fetch_changelog",
"mcp__api-changelog-tracker__diff_versions",
"mcp__api-changelog-tracker__search"
],
"ask": [
"mcp__api-changelog-tracker__detect_breaking_changes",
"mcp__api-changelog-tracker__subscribe_feed"
],
"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 api-changelog-tracker. Review it before you use it.
Capability tags behind 1 rule
- mcp__api-changelog-tracker__subscribe_feed outbound
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.lazymac2x/api-changelog-tracker/verify?hash=e480de18482b5256e7343bee086619f44588330737b8c2f455cb746132f072ff" | jq -e '.changed == false'Pinned hash e480de18482b, from Nov 21, 2026, 14: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.lazymac2x/api-changelog-tracker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lazymac2x/api-changelog-tracker)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
api-changelog-tracker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the api-changelog-tracker MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 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 api-changelog-tracker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the api-changelog-tracker 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 api-changelog-tracker MCP server have?
- 6 tools: 2 write, 4 read. detect_breaking_changes, subscribe_feed, list_tracked_apis, fetch_changelog, diff_versions and search.
Does the api-changelog-tracker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the api-changelog-tracker MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): subscribe_feed.
Has the api-changelog-tracker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.