io.github.lazymac2x/api-perf-analyzer is an MCP server published by io.github.lazymac2x, hosted at api.lazy-mac.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 4 tools, including perf_analyze, cache_opportunity, bottleneck_detect, optimization_suggest.
Cloudflare Workers MCP server: api-perf-analyzer
160 connections through 5 shared values. Tap any node.
Grade API response time (A–D), compute throughput and data efficiency, get targeted recommendations.
| Parameter | Type | Description |
|---|---|---|
| dataSize | number | Response body bytes (default: 1) |
| errorRate | number | Error rate 0–1 (default: 0) |
| requestCount | number | Parallel request count (default: 1) |
| responseTime * | number | Response time in milliseconds (> 0) |
{
"name": "perf_analyze",
"description": "Grade API response time (A–D), compute throughput and data efficiency, get targeted recommendations.",
"inputSchema": {
"type": "object",
"required": [
"responseTime"
],
"properties": {
"dataSize": {
"type": "number",
"description": "Response body bytes (default: 1)"
},
"errorRate": {
"type": "number",
"description": "Error rate 0–1 (default: 0)"
},
"requestCount": {
"type": "number",
"description": "Parallel request count (default: 1)"
},
"responseTime": {
"type": "number",
"description": "Response time in milliseconds (> 0)"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Detect missing or suboptimal HTTP caching headers and get prioritized fixes.
| Parameter | Type | Description |
|---|---|---|
| headers | object | HTTP response headers as key-value object |
| dataSize | number | Response body size in bytes |
{
"name": "cache_opportunity",
"description": "Detect missing or suboptimal HTTP caching headers and get prioritized fixes.",
"inputSchema": {
"type": "object",
"properties": {
"headers": {
"type": "object",
"description": "HTTP response headers as key-value object"
},
"dataSize": {
"type": "number",
"description": "Response body size in bytes"
}
}
}
}Identify which component (DB, external API, compute) is the dominant latency source.
| Parameter | Type | Description |
|---|---|---|
| computeTime | number | Time on in-process computation in ms |
| databaseTime | number | Time on DB queries in ms |
| responseTime * | number | Total response time in ms |
| externalApiTime | number | Time on external API calls in ms |
{
"name": "bottleneck_detect",
"description": "Identify which component (DB, external API, compute) is the dominant latency source.",
"inputSchema": {
"type": "object",
"required": [
"responseTime"
],
"properties": {
"computeTime": {
"type": "number",
"description": "Time on in-process computation in ms"
},
"databaseTime": {
"type": "number",
"description": "Time on DB queries in ms"
},
"responseTime": {
"type": "number",
"description": "Total response time in ms"
},
"externalApiTime": {
"type": "number",
"description": "Time on external API calls in ms"
}
}
}
}Get a prioritized, actionable optimization plan. Accepts raw metrics or the output of perf_analyze.
| Parameter | Type | Description |
|---|---|---|
| grade | string | From perf_analyze output (optional) |
| dataSize | number | |
| errorRate | number | |
| responseTime | number | |
| dataEfficiency | number | From perf_analyze output (optional) |
{
"name": "optimization_suggest",
"description": "Get a prioritized, actionable optimization plan. Accepts raw metrics or the output of perf_analyze.",
"inputSchema": {
"type": "object",
"properties": {
"grade": {
"type": "string",
"description": "From perf_analyze output (optional)"
},
"dataSize": {
"type": "number"
},
"errorRate": {
"type": "number"
},
"responseTime": {
"type": "number"
},
"dataEfficiency": {
"type": "number",
"description": "From perf_analyze output (optional)"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.