Ext Ops Panel
Open dashboard
Comparison

hub-meta vs Indicate

hub-meta is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

hub-meta is a plugin bundle for AI coding tools published by AI Hub Contributors. No marketplace we read lists it any more. Indicate is an MCP server published by indicateio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacehub-metaIndicate
Community marketplace dodobrands/ai-hub Removed on 2026-10-23
Version: 1.2.3
Forks (GitHub): 8
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
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

hub-meta vs Indicate
Facthub-metano longer listed · Indicate
Marketplaces that list it (differs)01
Stars (GitHub) (differs)8No figure on GitHub
Forks (GitHub) (differs)8No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (industry.indicate-data.io/agent/semantic/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/dodobrands/ai-hubgithub.com/indicateio/indicate-vscode
Changes in the last 7 days (differs)30
First seen (differs)2026-10-162026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago, requires a key

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of hub-meta

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • utils

    Core AIWG utilities for context regeneration and workspace management.

    by AIWG Contributors · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • aria-knowledge

    Knowledge management, decision discipline, codebase understanding, plan pre-mortems, and release retrospectives for Claude Code

    by Mike Prasad · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • PAPI: Persistent Adaptive Project Intelligence

    Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.

    by getpapi · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces · Describes nearly the same job

  • ai-ready

    Analyze any repository and generate AI-ready configuration — AGENTS.md, copilot-instructions.md, CI workflows, issue templates, and more. Mines your PR review patterns and creates…

    by johnpapa · Plugin bundle

    Listed on: Copilot CLI: github/awesome-copilot, Community GitHub marketplaces · Describes nearly the same job

  • Umtri

    Give your AI agent a persistent map of your project's structure, dependencies, and bugs.

    by umtri.io · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Dev Tools

    Dev-tools — scaffold repos, multi-agent QA review, templatize. Session-handover commands and agent moved to claude-hopper in 1.2.0.

    by danielrosehill · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

hub-meta

In its own words, on Community GitHub marketplaces:

AI Hub meta-tools — setup wizard, create new commands, run session retrospectives, update subtree from upstream

Indicate

In its own words, on Official MCP Registry:

AI-powered intelligence for your development workflow via Indicate.

How to run each

hub-meta

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

Indicate As a remote MCP server

Claude Code
claude mcp add --transport http indicate-mcp https://industry.indicate-data.io/agent/semantic/mcp --header "Authorization: Bearer <YOUR_INDICATE_API_KEY>"

Requires: Authorization header

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

Only Indicate 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: hub-meta · What it can do: Indicate · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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