weckr vs Argus API Spend
weckr is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
weckr is a plugin bundle for AI coding tools published by Ghiles Asmani. No marketplace we read lists it any more. Argus API Spend is an MCP server published by argus.town. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace ghiles3232/weckr-sdks | Removed on 2026-10-23 Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | weckrno longer listed · | Argus API Spend |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.argus.town/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ghiles3232/weckr-sdks | Not stated |
| Changes in the last 7 days (differs) | 2 | 5 |
| First seen (differs) | 2026-10-13 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-23 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of weckr
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Price a Claude, GPT, Gemini or Grok call before you send it. Runs locally.
-
LLM API Pricing and Automation Tools by shurco.ai
Daily LLM API prices, cost estimates and automation ROI tools from shurco.ai
-
LLM cost optimizer for OpenAI, Anthropic, token usage, BYOK, and SkillFM Beacon audits.
-
focxle — what your AI agents cost
Ask what your AI agents cost. Per agent, across every vendor, from your editor.
-
Read-only source-linked AI API prices, comparisons, cost estimates, and price changes.
-
ai-economics pl.piszczek/ai-economics
12 calculators for AI cost, energy and agent verification. Free API, no key.
What each says it does
weckr
The Weckr cost and margin toolkit for your AI assistant: integrate the SDK, look up current LLM token prices, estimate what an AI feature costs per user before you ship, and audit which pricing plans are unprofitable at today's model prices.
Argus API Spend
Track API spend, credit balances and runway across OpenAI, Anthropic, OpenRouter and 25 more.
How to run each
weckr
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Argus API Spend As a remote MCP server
claude mcp add --transport http argus https://api.argus.town/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Argus API Spend has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: weckr · What it can do: Argus API Spend · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.