Skip to content

api-flow-analyzer MCP server

io.github.lazymac2x/api-flow-analyzerlazymac2xstreamable-httpv1.0.0Scanned

Cloudflare Workers MCP server: api-flow-analyzer

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 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

5 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-flow-analyzer MCP server can do

The api-flow-analyzer MCP server is published by the GitHub account lazymac2x. It has 6 tools. It can create or change data (5 tools: track_call, detect_redundancy, suggest_batching, calculate_savings and 1 more), but cannot delete data. 1 tool only reads.

1 tool can send data out of your system (track_call).

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

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 metadataCan send data outNo findings

    Why it is in this group

    • The name "track_call" says "call": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Record and track an individual API call with metadata
Only reads 1Show 1 read-only tool
  • 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.

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.

Tools listed without sign-in

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
5
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-flow-analyzer/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.lazy-mac.com/api-flow-analyzer/mcp: tools/list returned 6 tools to an anonymous client, including track_call (write), detect_redundancy (write), suggest_batching (write), calculate_savings (write), get_dependency_graph (write)

    What this check looks for

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-flow-analyzer https://api.lazy-mac.com/api-flow-analyzer/mcp
claude mcp add --transport http api-flow-analyzer https://api.lazy-mac.com/api-flow-analyzer/mcp

Run 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.

.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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as api-flow-analyzer. Review it before you use it.

Capability tags behind 1 rule
  • mcp__api-flow-analyzer__track_call 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-flow-analyzer/verify?hash=feafcd6c601c2e1088307c6401a7bad1a5a4a6a1f3327053978d5e25af5a44ac" | jq -e '.changed == false'

Pinned hash feafcd6c601c, 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-flow-analyzer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.lazymac2x/api-flow-analyzer
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.lazymac2x/api-flow-analyzer.svg)](https://radar.anlyon.com/servers/io.github.lazymac2x/api-flow-analyzer)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.

api-flow-analyzer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the api-flow-analyzer MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 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-flow-analyzer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the api-flow-analyzer 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-flow-analyzer MCP server have?

6 tools: 5 write, 1 read. track_call, detect_redundancy, suggest_batching, calculate_savings, get_dependency_graph and analyze_flow.

Does the api-flow-analyzer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the api-flow-analyzer 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): track_call.

Has the api-flow-analyzer MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.