Api Response Cost Analyzer

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

Cloudflare Workers MCP server: api-response-cost-analyzer

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint named api-response-cost-analyzer, hosted on Cloudflare Workers, that appears to analyze API response costs.

What you can do
The registry lists this as a Cloudflare Workers MCP server called api-response-cost-analyzer, reachable over streamable HTTP at a remote endpoint. No tools, packages, or documentation are published, so the specific operations it exposes to an assistant are not described in the available material. Its name suggests analysis of API response cost, but that is not confirmed by any listed capability.
When to use it
Consider it only if you specifically want a hosted endpoint for API response cost analysis and are willing to test an undocumented server. Because no tools or README are provided, there is little basis to judge whether it fits a given workflow.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the provider's endpoint. No authentication, environment variables, headers, or local runtime are declared.
Before you install
No authentication is declared, so any data sent to the remote endpoint is handled by a third party without a stated credential check. The server's tools and behavior are undocumented, so verify what it does before sending sensitive API responses or credentials.

Installation

In SourceWeft

  1. Open Api Response Cost Analyzer 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-response-cost-analyzer/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-response-cost-analyzer": {
      "type": "http",
      "url": "https://api.lazy-mac.com/api-response-cost-analyzer/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

analyze_response

Analyze API response content and estimate token count

Parameterscontentrequired

estimate_cost

Estimate API response cost for a specific LLM model

Parametersmodelrequiredcontentrequiredinput_tokens

compare_models

Compare API response costs across multiple LLM models

Parametersmodelscontentrequiredinput_tokens

optimize_payload

Get optimization suggestions to reduce API response cost

Parameterscontentrequired

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.