io. github. lazymac2x/ api-flow-analyzer
by lazymac2x · remote · no sign-in to list tools · v1.0.0 · published by GitHub user lazymac2x
Cloudflare Workers MCP server: api-flow-analyzer
6 tools: 5 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things5Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
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-flow-analyzer https://api.lazy-mac.com/api-flow-analyzer/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
6 tools
Changes things 5Claude Code: ask
calculate_savingsCalculate estimated cost and latency savings from optimizationsNo 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 Calculate estimated cost and latency savings from optimizations
detect_redundancyIdentify duplicate or redundant API calls in a flowNo 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 duplicate or redundant API calls in a flow
get_dependency_graphGenerate dependency graph of API calls showing call sequence and relationshipsNo findings
Why it is in this group
- The name "get_dependency_graph" says "get": a word for reading.
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate dependency graph of API calls showing call sequence and relationships
suggest_batchingRecommend batching opportunities for parallel API callsNo 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 Recommend batching opportunities for parallel API calls
track_callRecord and track an individual API call with metadataNo findings
Why it is in this group
- The name "track_call" says "call": a word for a change.
Description, as the server wrote it Record and track an individual API call with metadata
Only reads 1Claude Code: allow
analyze_flowAnalyze complete API call flow and identify patternsNo findings
Why it is in this group
- The name "analyze_flow" says "analyze": a word for reading.
Description, as the server wrote it Analyze complete API call flow and identify patterns
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-flow-analyzer https://api.lazy-mac.com/api-flow-analyzer/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__api-flow-analyzer__analyze_flow"
],
"ask": [
"mcp__api-flow-analyzer__track_call",
"mcp__api-flow-analyzer__detect_redundancy",
"mcp__api-flow-analyzer__suggest_batching",
"mcp__api-flow-analyzer__calculate_savings",
"mcp__api-flow-analyzer__get_dependency_graph"
],
"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-flow-analyzer. Review it before you use it.
