Ext Ops Panel
Open dashboard
Comparison

yabadoo-mcp vs io.github.seunghan91/ainote

yabadoo-mcp is an MCP server published by HENRIQUE4345. Marketplaces we read that list it: 1 (PyPI (MCP servers)). io.github.seunghan91/ainote is an MCP server published by seunghan91. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
Marketplaceyabadoo-mcpio.github.seunghan91/ainote
PyPI (MCP servers) Listed
Version: 0.14.0
Downloads/month (PyPI): 368
Downloads/week (PyPI): 988
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.2
Downloads/month (npm): 1 184
Downloads/week (npm): 650
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.3.7
Downloads/month (npm): 1 184
Downloads/week (npm): 650
Forks (GitHub): 1
Stars (GitHub): 1
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

yabadoo-mcp vs io.github.seunghan91/ainote
Factyabadoo-mcpio.github.seunghan91/ainote
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub1
Last release (differs)Not published2026-11-03
Where it runs (differs)On your machine (yabadoo-mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/henrique4345/yabadoo-braingithub.com/seunghan91/ainote
Changes in the last 7 days (differs)01
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h ago

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

yabadoo-mcp

In its own words, on PyPI (MCP servers):

Yabadoo MCP server: a personal second brain connected to Claude

io.github.seunghan91/ainote

In its own words, on Official MCP Registry:

Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.

How to run each

yabadoo-mcp

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

io.github.seunghan91/ainote As a remote MCP server

Claude Code
claude mcp add --transport http ainote https://api.ainote.dev/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: AINOTE_API_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.seunghan91/ainote 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 yabadoo-mcp publish no settings it asks for, so we do not compare settings.

What it can do: yabadoo-mcp · What it can do: io.github.seunghan91/ainote · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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