Ai Economics

pl.piszczekPublished by piszczek.plv1.0.1Updated Oct 24, 2026

12 calculators for AI cost, energy and agent verification. Free API, no key.

VerifiedSTDIODesktop onlyFinance Data & Analytics AI & ML

Server details

Identifier: pl.piszczek/ai-economics
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to piszczek.pl. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/pl.piszczek%2Fai-economics.svg)](https://sourceweft.com/mcp/pl.piszczek%2Fai-economics?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server offering 12 calculators for AI token costs, energy use and agent verification, backed by a free stateless API.

What you can do: Estimate token and context-window costs across models, and compare routing to cheaper tiers for annual savings. Calculate agent-hour cost, token burn in money, kWh and CO2, and per-query electricity use. Compare model efficiency per verified task and estimate humanoid robot runtime per charge. Assess agent autonomy once proof is required, revocation exposure, review-team capacity and the cost of unverified work. Each response returns a result, formula, interpretation and a ready-to-quote citation sentence.
When to use it: Useful when planning or defending an AI budget: comparing model pricing, sizing context windows, estimating energy and emissions, or arguing about how autonomous an agent really is. Good for quick, citable numbers in proposals and reviews.
Requirements: Runs locally over stdio, typically via npx with the npm package, so Node.js is needed. No account or API key is required. The optional AI_ECONOMICS_API environment variable overrides the default API base URL, for example to point at a self-hosted instance. Network access to that API is needed.

Before you install

Inputs are sent to the third-party piszczek.pl API, which the README describes as stateless and not storing inputs; avoid submitting confidential figures. Results are model estimates based on defaults and assumptions, so verify them before quoting in budgets or reviews. The API base URL can be redirected via AI_ECONOMICS_API, so confirm it points where you expect.

Installation

In SourceWeft

Open Ai Economics in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ai-economics-mcp

[DOI]

[npm] [Glama score] [MIT]

MCP server for AI economics. Gives Claude, Cursor and any MCP client 12 calculators for the questions that decide AI budgets: what tokens cost, what queries burn, and whether agent work can be proven.

Listed in the official MCP Registry as pl.piszczek/ai-economics (domain-verified). Wraps the free piszczek.pl/tools API — no key, no sign-up, stateless (inputs are never stored). The math is the same as the interactive calculators.

Install

Claude Desktop / Claude Code (claude_desktop_config.json / .mcp.json):

json

{  "mcpServers": {    "ai-economics": {      "command": "npx",      "args": ["-y", "@michalpiszczek/ai-economics-mcp"]    }  }}

{  "mcpServers": {    "ai-economics": {      "command": "npx",      "args": ["-y", "@michalpiszczek/ai-economics-mcp"]    }  }}

Claude Code one-liner:

Tools

Tool	Answers
`token_cost`	What do 1M tokens cost per month across GPT, Claude, Gemini, DeepSeek?
`context_window`	How many tokens is 50 pages, does it fit, what does carrying it cost?
`agent_hour`	What does one hour of an AI agent cost, fully loaded with verification?
`model_routing`	How much does routing to a cheaper tier save per year?
`llm_energy`	How much electricity does an AI query use?
`joules_per_verified_task`	Which model is most efficient per task that actually passes?
`token_burn`	What does org-wide token burn cost in money, kWh, CO₂?
`humanoid_energy`	How long can a humanoid robot run per charge?
`proof_adjusted_autonomy`	How autonomous is a "90% autonomous" agent once proof is required?
`revocation_exposure`	How long does a revoked token keep working across your stack?
`verification_bottleneck`	How many AI agents can a human review team absorb?
`proof_debt`	What does unverified AI work cost over time?

All parameters are optional; defaults mirror the interactive calculators. Every response includes result, formula, interpretation and a ready-to-quote cite_as sentence.

Example

You: how autonomous is our agent really? it completes 90% alone, evidence for 95%, 80% independently validated, 90% on time

Claude (calls proof_adjusted_autonomy): PAA = 61.6% — supervised autonomy. The gap vs the claimed 90% is 28.4 pp, and the biggest lever is independent validation…

Configuration

Glama builds and releases

Glama generates its own Dockerfile from the build configuration. Use these settings:

Build steps: ["npm ci --omit=dev"]
CMD arguments: ["mcp-proxy", "--", "node", "index.js"]
Environment variables: optional AI_ECONOMICS_API; no credentials required.

This is plain JavaScript: there is no build script or compilation step. Do not use pnpm run build or npm run build. After syncing the repository, build the selected commit and publish a Glama release from the successful test. A GitHub or npm release alone does not trigger Glama's quality evaluation.

For local stdio use, the repository Dockerfile needs no proxy or exposed ports:

Concepts behind the tools

Joule Wars — the AI race for energy efficiency
Proof-Adjusted Autonomy — the metric of proven agent work
Revocation Exposure — how long revoked authority keeps working

Citing a result

Every tool response carries a cite_as sentence written to be quoted verbatim. For a document that has to survive review, DOIs and BibTeX for this server, the calculators and the three concepts they instrument are at piszczek.pl/cite.

License

MIT. Concepts and calculators by Michał Piszczek (CC BY 4.0 — attribution appreciated).

Source: README.md at commit 147904b

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts