Skip to content

io.github.lazymac2x/api-payload-auditor

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

Cloudflare Workers MCP server: api-payload-auditor

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-payload-auditor https://api.lazy-mac.com/api-payload-auditor/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
  • bandwidth_cost_calcCalculate cloud API egress bandwidth costs for a given payload size and monthly traffic.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
    Calculate cloud API egress bandwidth costs for a given payload size and monthly traffic. Returns cost at 25%, 50%, and 75% reduction scenarios.
  • field_prune_suggestIdentify and suggest unnecessary fields for removal from a JSON payload.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 and suggest unnecessary fields for removal from a JSON payload. Flags debug/temp/internal/deprecated fields, null values, empty arrays, and _ prefix fields.
Only reads 2Claude Code: allow
  • compare_payloadsCompare an original payload to an optimized version.No findings

    Why it is in this group

    • The name "compare_payloads" says "compare": a word for reading.
    Description, as the server wrote it
    Compare an original payload to an optimized version. Returns size reduction %, removed field paths, and depth change.
  • payload_analyzeAnalyze a JSON API response payload structure — field count, size in bytes, max nesting depth, type distribution, null field count, and redundancy signals (empty arrays, null value…No findings

    Why it is in this group

    • The name "payload_analyze" says "analyze": a word for reading.
    Description, as the server wrote it
    Analyze a JSON API response payload structure — field count, size in bytes, max nesting depth, type distribution, null field count, and redundancy signals (empty arrays, null values).

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 or outbound.

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

Install

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

claude mcp add --transport http api-payload-auditor https://api.lazy-mac.com/api-payload-auditor/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-payload-auditor__payload_analyze",
      "mcp__api-payload-auditor__compare_payloads"
    ],
    "ask": [
      "mcp__api-payload-auditor__field_prune_suggest",
      "mcp__api-payload-auditor__bandwidth_cost_calc"
    ],
    "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-payload-auditor. Review it before you use it.