Is the Lazymac2x Api Changelog Tracker MCP server down?

mcp-registry/io.github.lazymac2x/api-changelog-tracker · v1.1.0

healthy
Last checked 2026-10-18 18:02 UTC · handshake 96ms

As of 2026-10-18 18:02 UTC, the Lazymac2x Api Changelog Tracker MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 14 minutes.

uptime (30d checks)
100%
checks observed
3,697
outages (90d)
1
tools
6

Cloudflare Workers MCP server: api-changelog-tracker

Install Lazymac2x Api Changelog Tracker MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lazymac2x-api-changelog-tracker-mcp-serv https://api.lazy-mac.com/api-changelog-tracker/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lazymac2x-api-changelog-tracker-mcp-serv": {
      "type": "http",
      "url": "https://api.lazy-mac.com/api-changelog-tracker/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 3 warning(s) across 6 tool(s); ~794 tokens of tool definitions.
Scores higher than 9% of 15,333 MCP servers Glimind has audited.
Its tool list costs an agent ~794 tokens per session — lighter than 80% of servers.
73 → 73 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (4)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: detect_breaking_changes, diff_versions, fetch_changelog, list_tracked_apis, search and 1 more

3 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: detect_breaking_changes, diff_versions, subscribe_feed

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker/fixes

fetch_changelog 1 change
{
  "name": "fetch_changelog",
  "description": "Fetch versioned changelog entries for a specific API (openai, anthropic, stripe, github, twilio, cloudflare, sendgrid, slack). Filter by date and breaking-only.",
  "inputSchema": {
    "type": "object",
    "required": [
      "api_id"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "description": "Max entries to return (default 10, max 50)"
      },
      "since": {
        "type": "string",
        "description": "Return entries on or after this date (ISO 8601)"
      },
      "api_id": {
        "type": "string",
        "description": "API identifier"
      },
      "breaking_only": {
        "type": "boolean",
        "description": "Return only entries with breaking changes"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_tracked_apis 1 change
{
  "name": "list_tracked_apis",
  "description": "List all tracked APIs with metadata and latest changelog status. Filter by category (ai, payments, developer-tools, communications, infrastructure, email).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "category": {
        "type": "string",
        "description": "Filter by category"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
search 1 change
{
  "name": "search",
  "description": "Full-text search across all changelog entries. Searches title, summary, and change descriptions.",
  "inputSchema": {
    "type": "object",
    "required": [
      "q"
    ],
    "properties": {
      "q": {
        "type": "string",
        "description": "Search query"
      },
      "limit": {
        "type": "number",
        "description": "Max results (default 20, max 100)"
      },
      "api_id": {
        "type": "string",
        "description": "Limit search to a specific API"
      },
      "breaking_only": {
        "type": "boolean",
        "description": "Return only breaking change entries"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lazymac2x/api-changelog-tracker"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/api-changelog-tracker"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-changelog-tracker?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f259cc01ff429695…, first seen 2026-10-17, included at leaf 2644 of 22,995. Version history · verify what your client received.

Tools (6)

Compare: most reliable devops servers · most reliable knowledge servers · most reliable retrieval servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lazymac2x Api Changelog Tracker MCP server down right now?

As of 2026-10-18 18:02 UTC, the Lazymac2x Api Changelog Tracker MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 14 minutes.

How many tools does Lazymac2x Api Changelog Tracker MCP server provide?

Lazymac2x Api Changelog Tracker MCP server advertises 6 tools, including detect_breaking_changes, diff_versions, fetch_changelog, list_tracked_apis, search.

How do I install Lazymac2x Api Changelog Tracker MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/api-changelog-tracker/mcp

Is the Lazymac2x Api Changelog Tracker MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lazymac2x Api Changelog Tracker MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.