Openclaw Cost Tracker Mcp

io.github.temurkhan13Published by GitHub account temurkhan13v1.1.3Updated Oct 30, 2026

AI agent token-cost telemetry + 429 prediction. Per-agent attribution, anomaly + routing + quota.

The publisher's own server: OpenClaw Direct

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Local MCP server that gives an assistant token-cost telemetry for AI agents, with per-agent attribution, anomaly detection, routing hints and 429 prediction.

What you can do
  • Report token cost and usage telemetry for AI agents.
  • Break spending down by individual agent for attribution.
  • Flag cost anomalies and suggest routing decisions.
  • Predict rate-limit (429) conditions and track quota.
When to use it
Useful when you run several AI agents and want an assistant to watch token spend, attribute costs per agent, and anticipate rate limits or quota exhaustion. Best suited to local desktop setups where cost data is already being collected.
Requirements
Runs as a local process on the user's machine over stdio, installed from the PyPI package openclaw-cost-tracker-mcp, so a Python environment is needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The tool list is not published, so what the assistant can read or change is unclear before install. Cost and usage telemetry may reveal which agents and workloads you run; review what data it collects and where it is stored. No credentials are declared, but verify the package source before running it locally.

Installation

In SourceWeft

  1. Open Openclaw Cost Tracker Mcp in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

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

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

25% 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

    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 Openclaw integrations