Ext Ops Panel
Open dashboard
Comparison

waldo-fyi vs Aiso

waldo-fyi is a plugin bundle for AI coding tools published by waldo-fyi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Aiso is an MCP server published by BenUsername. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplacewaldo-fyiAiso
Claude Code: claude-plugins-community Listed
Version: 1.4.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

waldo-fyi vs Aiso
Factwaldo-fyiAiso
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.waldo.fyi/strategy)Remote server (app.getaiso.com/api/v1/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)18Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/waldo-fyi/waldo-claude-pluginNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-24
Endpoint at the last check (differs)Responded 4 days agonot checked yet

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

waldo-fyi

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

Waldo strategy agent skills for ad intelligence, social listening, web research, data analysis, and archival knowledge — powered by the Waldo MCP connector

Aiso

In its own words, on Official MCP Registry:

Inspect AI brand visibility, tracked prompts, competitors, citations and search fan-outs.

How to run each

waldo-fyi As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install waldo-fyi@claude-community

Aiso As a remote MCP server

Claude Code
claude mcp add --transport http aiso https://app.getaiso.com/api/v1/mcp --header "x-api-key: <YOUR_X_API_KEY>"

Requires: x-api-key header

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

Only waldo-fyi 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: waldo-fyi · What it can do: Aiso · 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