Api Payload Auditor

io.github.lazymac2xPublished by GitHub account lazymac2xv1.0.0Updated Oct 25, 2026

Cloudflare Workers MCP server: api-payload-auditor

The publisher's own server: Video Transcript

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

A remote MCP server that audits JSON API response payloads: structure analysis, field pruning suggestions, egress cost estimates and before/after comparison.

What you can do
Analyze a JSON payload's structure: field count, byte size, nesting depth, type distribution, nulls and redundancy signals such as empty arrays and null values. Suggest fields to prune, flagging debug, temp, internal, deprecated, null, empty-array and underscore-prefixed fields. Estimate cloud API egress bandwidth costs for a payload size and monthly traffic, with 25%, 50% and 75% reduction scenarios. Compare an original payload with an optimized version to get size reduction percentage, removed field paths and depth change.
When to use it
Useful when trimming oversized or bloated JSON API responses, reviewing payload shape before optimizing an endpoint, or putting rough numbers on egress bandwidth costs and the savings from cutting fields.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. The assistant needs network access to the hosted endpoint.
Before you install
Payloads you submit are sent to a third-party hosted service, so avoid sending sensitive or production data. The cost figures are estimates based on the size and traffic you supply, not billing data. The tools only analyze and suggest; they do not modify your API.

Installation

In SourceWeft

  1. Open Api Payload Auditor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lazymac2x%2Fapi-payload-auditor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "api-payload-auditor": {
      "type": "http",
      "url": "https://api.lazy-mac.com/api-payload-auditor/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

payload_analyze

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

Parameterspayloadrequired

field_prune_suggest

Identify and suggest unnecessary fields for removal from a JSON payload. Flags debug/temp/internal/deprecated fields, null values, empty arrays, and _ prefix fields.

Parameterspayloadrequiredthreshold

bandwidth_cost_calc

Calculate cloud API egress bandwidth costs for a given payload size and monthly traffic. Returns cost at 25%, 50%, and 75% reduction scenarios.

ParametersregionmonthlyRequestspayloadSizeBytesrequired

compare_payloads

Compare an original payload to an optimized version. Returns size reduction %, removed field paths, and depth change.

Parametersoriginalrequiredoptimizedrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Payload integrations