Ext Ops Panel
Open dashboard
Comparison

ai.kavel/kavel-mcp vs dev.rostro/rostro

ai.kavel/kavel-mcp is an MCP server published by kavel.ai. Marketplaces we read that list it: 1 (Official MCP Registry). dev.rostro/rostro is an MCP server published by rostro.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
Marketplaceai.kavel/kavel-mcpdev.rostro/rostro
Official MCP Registry Listed
Version: 0.2.0
Downloads/month (npm): 263
Downloads/week (npm): 115
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

ai.kavel/kavel-mcp vs dev.rostro/rostro
Factai.kavel/kavel-mcpdev.rostro/rostro
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-14Not published
Where it runs (differs)Remote server (www.kavel.ai/api/mcp)Remote server (proto.rostro.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/hanshs474/kavel-mcpgithub.com/francis-ros/rostro-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 4 days ago returned HTTP 405Status out of date: last check 5 days ago returned HTTP 307

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

ai.kavel/kavel-mcp

In its own words, on Official MCP Registry:

Discover Kavel's AI photo/video generators, get tuned prompts, and open the right tool on kavel.ai.

dev.rostro/rostro

In its own words, on Official MCP Registry:

Turn any LLM multimodal; generate images, voices, videos, 3D models, music, and more.

How to run each

ai.kavel/kavel-mcp As a remote MCP server

Claude Code
claude mcp add --transport http kavel-mcp https://www.kavel.ai/api/mcp

dev.rostro/rostro As a remote MCP server

Claude Code
claude mcp add --transport http rostro https://proto.rostro.dev/mcp

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

Only the endpoint of ai.kavel/kavel-mcp responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of dev.rostro/rostro nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: ai.kavel/kavel-mcp · What it can do: dev.rostro/rostro · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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