Ext Ops Panel
Open dashboard
Comparison

Kin vs io.github.pintomatic/kernal-mcp

Kin is an MCP server published by kinlab.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pintomatic/kernal-mcp is an MCP server published by pintomatic. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceKinio.github.pintomatic/kernal-mcp
Official MCP Registry Listed
Version: 0.9.1
Downloads/month (npm): 1 086
Downloads/week (npm): 156
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 144
Downloads/week (npm): 49
Forks (GitHub): 0
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

Kin vs io.github.pintomatic/kernal-mcp
FactKinio.github.pintomatic/kernal-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Forks (GitHub)00
Last release (differs)2026-10-31Not published
Where it runs (differs)Remote server (app.kinlab.ai/mcp)On your machine (kernal-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/kinlab-ai/kin-plugingithub.com/pintomatic/kernal
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 45 h ago returned HTTP 401no remote endpoint we check

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

Kin

In its own words, on Official MCP Registry:

Connect accounts once. Set what agents may do per account. Enforced when the action runs.

io.github.pintomatic/kernal-mcp

In its own words, on Official MCP Registry:

Graph-native memory for AI agents: a knowledge graph built from conversation, via MCP.

How to run each

Kin As a remote MCP server

Claude Code
claude mcp add --transport http kin https://app.kinlab.ai/mcp

io.github.pintomatic/kernal-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio kernal-mcp -- npx -y kernal-mcp

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

Only Kin 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: Kin · What it can do: io.github.pintomatic/kernal-mcp · 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