Ext Ops Panel
Open dashboard
Comparison

weckr vs io.github.theluckystrike/amortization

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. io.github.theluckystrike/amortization is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceweckrio.github.theluckystrike/amortization
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.22.6
Forks (GitHub): 3
Stars (GitHub): 2
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 io.github.theluckystrike/amortization
Factweckrno longer listed · io.github.theluckystrike/amortization
Marketplaces that list it (differs)01
Stars (GitHub) (differs)82
Forks (GitHub) (differs)03
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ghiles3232/weckr-sdksgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

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.

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.

io.github.theluckystrike/amortization

In its own words, on Official MCP Registry:

Loan and lease schedules: payment, interest, early settlement and the journal, to the minor unit.

How to run each

weckr

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

io.github.theluckystrike/amortization As a remote MCP server

Claude Code
claude mcp add --transport http amortization https://mcp.zovo.one/mcp/amortization --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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

Only io.github.theluckystrike/amortization 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

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: io.github.theluckystrike/amortization · 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