Skip to content

io.github.lazymac2x/api-perf-analyzer

by lazymac2x · remote · no sign-in to list tools · v1.0.0 · published by GitHub user lazymac2x

Cloudflare Workers MCP server: api-perf-analyzer

Changes · 2
CompareRegistry entry

4 tools: 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http api-perf-analyzer https://api.lazy-mac.com/api-perf-analyzer/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 2Claude Code: ask
  • bottleneck_detectIdentify which component (DB, external API, compute) is the dominant latency source.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
    Identify which component (DB, external API, compute) is the dominant latency source.
  • cache_opportunityDetect missing or suboptimal HTTP caching headers and get prioritized fixes.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 missing or suboptimal HTTP caching headers and get prioritized fixes.
Only reads 2Claude Code: allow
  • optimization_suggestGet a prioritized, actionable optimization plan.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a prioritized, actionable optimization plan. Accepts raw metrics or the output of perf_analyze.
  • perf_analyzeGrade API response time (A–D), compute throughput and data efficiency, get targeted recommendations.No findings

    Why it is in this group

    • The name "perf_analyze" says "analyze": a word for reading.
    Description, as the server wrote it
    Grade API response time (A–D), compute throughput and data efficiency, get targeted recommendations.

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.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http api-perf-analyzer https://api.lazy-mac.com/api-perf-analyzer/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__api-perf-analyzer__perf_analyze",
      "mcp__api-perf-analyzer__optimization_suggest"
    ],
    "ask": [
      "mcp__api-perf-analyzer__cache_opportunity",
      "mcp__api-perf-analyzer__bottleneck_detect"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as api-perf-analyzer. Review it before you use it.