api-diff-monitor MCP server
io.github.lazymac2x/api-diff-monitorlazymac2xstreamable-httpv1.0.0Scanned
Cloudflare Workers MCP server: api-diff-monitor
6 tools: 1 can delete or cancel things, 2 change things and 3 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
3 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-diff-monitor MCP server can do
The api-diff-monitor MCP server is published by the GitHub account lazymac2x. It has 6 tools. It can delete or cancel things (1 tool: delete_endpoint) and create or change data (2 tools: register_endpoint and detect_breaking_changes). 3 tools only read.
1 tool can send data out of your system (register_endpoint).
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
Deletes or cancels 1Claude Code: deny
delete_endpointRemove a monitored endpoint and all its snapshots and diff history.No findings
Why it is in this group
- The name "delete_endpoint" says "delete": a word for removing or ending something.
Description, as the server wrote it Remove a monitored endpoint and all its snapshots and diff history.
Changes things 2Claude Code: ask
detect_breaking_changesCheck if a registered endpoint has had any breaking changes (removed fields or type changes).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 Check if a registered endpoint has had any breaking changes (removed fields or type changes).
register_endpointRegister an API endpoint to monitor for schema changes.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Register an API endpoint to monitor for schema changes. Provide name, url, and optionally method/headers/description.
Only reads 3Show 3 read-only tools
compare_snapshotsFetch a registered endpoint and compare against its last snapshot to detect schema changes.No findings
Why it is in this group
- The name "compare_snapshots" says "compare": a word for reading.
Description, as the server wrote it Fetch a registered endpoint and compare against its last snapshot to detect schema changes. Or compare two inline JSON objects directly.
get_diff_historyRetrieve the schema diff history for a registered endpoint.No findings
Why it is in this group
- The name "get_diff_history" says "get": a word for reading.
Description, as the server wrote it Retrieve the schema diff history for a registered endpoint.
list_monitored_endpointsList all registered API endpoints being monitored.No findings
Why it is in this group
- The name "list_monitored_endpoints" says "list": a word for reading.
Description, as the server wrote it List all registered API endpoints being monitored.
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
- 3
- 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-diff-monitor/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 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-diff-monitor/mcp: tools/list returned 6 tools to an anonymous client, including delete_endpoint (destructive), register_endpoint (write), detect_breaking_changes (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-diff-monitor https://api.lazy-mac.com/api-diff-monitor/mcpclaude mcp add --transport http api-diff-monitor https://api.lazy-mac.com/api-diff-monitor/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-diff-monitor__list_monitored_endpoints",
"mcp__api-diff-monitor__compare_snapshots",
"mcp__api-diff-monitor__get_diff_history"
],
"ask": [
"mcp__api-diff-monitor__register_endpoint",
"mcp__api-diff-monitor__detect_breaking_changes"
],
"deny": [
"mcp__api-diff-monitor__delete_endpoint"
]
}
}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-diff-monitor. Review it before you use it.
Capability tags behind 1 rule
- mcp__api-diff-monitor__register_endpoint 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-diff-monitor/verify?hash=dc88bd49b4b037d4a8b0485c353a6893e23accb59b75307da2a0d5665d65922d" | jq -e '.changed == false'Pinned hash dc88bd49b4b0, 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-diff-monitor/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lazymac2x/api-diff-monitor)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
api-diff-monitor MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the api-diff-monitor MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 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-diff-monitor MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_endpoint.
Can the api-diff-monitor 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-diff-monitor MCP server have?
- 6 tools: 1 destructive, 2 write, 3 read. delete_endpoint, register_endpoint, detect_breaking_changes, list_monitored_endpoints, compare_snapshots and get_diff_history.
Does the api-diff-monitor MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the api-diff-monitor 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): register_endpoint.
Has the api-diff-monitor MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.