Ext Ops Panel
Open dashboard
Comparison

steering-log vs io.github.jinsim/f1verse

steering-log is a plugin bundle for AI coding tools published by hanlogy. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.jinsim/f1verse is an MCP server published by jinsim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacesteering-logio.github.jinsim/f1verse
Claude Code: claude-plugins-community Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.14.0
Downloads/month (PyPI): 225
Downloads/week (PyPI): 41
Forks (GitHub): 0
Stars (GitHub): 0
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

steering-log vs io.github.jinsim/f1verse
Factsteering-logio.github.jinsim/f1verse
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (f1verse)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)5Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/hanlogy/steering-loggithub.com/jinsim/f1verse
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

steering-log

In its own words, on Claude Code: claude-plugins-community:

A Claude Code plugin that automatically detects and logs human steering moments from AI-assisted development sessions.

io.github.jinsim/f1verse

In its own words, on Official MCP Registry:

Formula 1 race data with the domain rules applied: stints, tyre wear, publish-safety. Zero deps.

How to run each

steering-log As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install steering-log@claude-community

io.github.jinsim/f1verse As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio f1verse -- uvx --from f1verse f1verse-mcp f1verse

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

Neither one's marketplaces publish the settings it asks for.

What it can do: steering-log · What it can do: io.github.jinsim/f1verse · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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