Ext Ops Panel
Open dashboard
Comparison

ingest-url vs CoreWise

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

ingest-url is a plugin bundle for AI coding tools published by Satyajeet Das. No marketplace we read lists it any more. CoreWise is an MCP server published by ryanportfolio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplaceingest-urlCoreWise
Community marketplace 123satyajeet123/ingest-url Removed on 2026-10-16
Version: 1.8.0
Forks (GitHub): 0
Stars (GitHub): 1
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

ingest-url vs CoreWise
Factingest-urlno longer listed · CoreWise
Marketplaces that list it (differs)01
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (corewise.video/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/123satyajeet123/ingest-urlNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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 ingest-url

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

  • vid2llm

    Read public videos (TikTok, YouTube, Instagram, X) as text. Pay per video with x402.

    by vid2llm.dev · MCP server

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

  • Video Extract

    Download any video from a URL, or get its transcript and key frames. All local, no API keys.

    by yanlinglabs.com · MCP server

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

  • LinkDigest — Xiaohongshu, Douyin, TikTok, YouTube to text

    Douyin, Xiaohongshu, TikTok, YouTube, X links to text: transcript, screen text, viral breakdown

    by linkdigest.dev · MCP server

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

  • Social → Context

    Turn a TikTok/Instagram/YouTube link into text for your AI: metadata, transcript and image OCR.

    by mcp-dir · MCP server

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

  • Instagram, Facebook, X, Reddit & Podcast Transcripts

    Transcribe Instagram Reels, Facebook, X and Reddit videos, podcasts (RSS, Apple) and any video URL.

    by LMSlay · MCP server

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

  • MarkGrab

    Universal web content extraction — any URL to LLM-ready markdown. HTML, YouTube, PDF, DOCX.

    by ArkNill · MCP server

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

Its card, with similar plugins by marketplace

What each says it does

ingest-url

In its own words, on Community GitHub marketplaces:

Turn any URL (YouTube, reels, X, articles, PDFs) into agent-readable text, timestamps, and frames on disk

CoreWise

In its own words, on Official MCP Registry:

Extract structured insights from videos, podcasts, articles, and PDFs with multi-model AI

How to run each

ingest-url

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

CoreWise As a remote MCP server

Claude Code
claude mcp add --transport http corewise https://corewise.video/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only CoreWise 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: ingest-url · What it can do: CoreWise · 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