Ext Ops Panel
Open dashboard
Comparison

io.github.amorphous-one/amorphous vs io.github.richardofortune/tyrekick

io.github.amorphous-one/amorphous is an MCP server published by amorphous-one. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.richardofortune/tyrekick is an MCP server published by richardofortune. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.amorphous-one/amorphousio.github.richardofortune/tyrekick
Official MCP Registry Listed
Version: 0.1.8
Downloads/month (npm): 1 928
Downloads/week (npm): 227
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.1
Downloads/month (npm): 127
Downloads/week (npm): 28
Forks (GitHub): 4
Stars (GitHub): 3
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

io.github.amorphous-one/amorphous vs io.github.richardofortune/tyrekick
Factio.github.amorphous-one/amorphousio.github.richardofortune/tyrekick
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (amorphous-cli)On your machine (tyrekick-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/amorphous-one/amorphous-plugingithub.com/richardofortune/tyrekick
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.amorphous-one/amorphous

In its own words, on Official MCP Registry:

Build abstracts on Amorphous. An abstract can be anything.

io.github.richardofortune/tyrekick

In its own words, on Official MCP Registry:

Read and resolve human feedback pinned on your live prototype, straight from your coding agent.

How to run each

io.github.amorphous-one/amorphous As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio amorphous -- npx -y amorphous-cli mcp

io.github.richardofortune/tyrekick As a local MCP server: npm package

Claude Code
claude mcp add --env "TYREKICK_TOKEN=<YOUR_TYREKICK_TOKEN>" --env "TYREKICK_URL=<YOUR_TYREKICK_URL>" --transport stdio tyrekick -- npx -y tyrekick-mcp

Requires: TYREKICK_TOKEN (secret), TYREKICK_URL

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 io.github.amorphous-one/amorphous publish no settings it asks for, so we do not compare settings.

What it can do: io.github.amorphous-one/amorphous · What it can do: io.github.richardofortune/tyrekick · Compare two other plugins

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