Ext Ops Panel
Open dashboard
Comparison

weckr vs APIThreshold

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. APIThreshold is an MCP server published by apithreshold.ai. 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

Where each is published
MarketplaceweckrAPIThreshold
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: 0.1.0
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

weckr vs APIThreshold
Factweckrno longer listed · APIThreshold
Marketplaces that list it (differs)01
Stars (GitHub) (differs)8No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/apithreshold/apithreshold:0.1.0)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 3
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ghiles3232/weckr-sdksNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-11

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.

  • Tokeven Cost Advisor

    Price a Claude, GPT, Gemini or Grok call before you send it. Runs locally.

    by tokeven.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • LLM API Pricing and Automation Tools by shurco.ai

    Daily LLM API prices, cost estimates and automation ROI tools from shurco.ai

    by shurco.ai · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • SkillFM LLM Cost Optimizer

    LLM cost optimizer for OpenAI, Anthropic, token usage, BYOK, and SkillFM Beacon audits.

    by ericm1018 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • focxle — what your AI agents cost

    Ask what your AI agents cost. Per agent, across every vendor, from your editor.

    by focxle.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • ai-economics pl.piszczek/ai-economics

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

    by piszczek.pl · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • ai-model-pricing io.github.DataLeadsPRO/ai-model-pricing

    Live pricing data for AI models across vendors: input/output prices per 1k tokens as JSON.

    by DataLeadsPRO · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

weckr

In its own words, on Community GitHub marketplaces:

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.

APIThreshold

In its own words, on Official MCP Registry:

Quality scoring and progressive gates for AI-generated API tests. Stripe/Twilio profiles. Free tier.

How to run each

weckr

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

APIThreshold As a local MCP server: Docker image

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "APITHRESHOLD_LICENSE=<YOUR_APITHRESHOLD_LICENSE>" --env "APITHRESHOLD_LLM_PROVIDER=<YOUR_APITHRESHOLD_LLM_PROVIDER>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio apithreshold -- docker run -i --rm -e ANTHROPIC_API_KEY -e APITHRESHOLD_LICENSE -e APITHRESHOLD_LLM_PROVIDER -e OPENAI_API_KEY ghcr.io/apithreshold/apithreshold:0.1.0 serve --transport stdio

Requires: ANTHROPIC_API_KEY (secret), APITHRESHOLD_LICENSE (secret), APITHRESHOLD_LLM_PROVIDER, OPENAI_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of weckr publish no settings it asks for, so we do not compare settings.

What it can do: weckr · What it can do: APIThreshold · 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.

Where the data comes from: how the catalog is built