Ext Ops Panel
Open dashboard
Comparison

Val Town vs io.github.daedalus/mcp-smart-proxy

Val Town is a plugin bundle for AI coding tools published by val-town. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). io.github.daedalus/mcp-smart-proxy is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceVal Townio.github.daedalus/mcp-smart-proxy
Claude Code: claude-plugins-official Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 10
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
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

Val Town vs io.github.daedalus/mcp-smart-proxy
FactVal Townio.github.daedalus/mcp-smart-proxy
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)10 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.val.town/v3/mcp)On your machine (mcp-smart-proxy)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/val-town/pluginsgithub.com/daedalus/mcp-smart-proxy
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Val Town

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

Build and deploy on Val Town. Bundles the Val Town MCP server and platform skills (HTTP vals, cron/intervals, SQLite, email, OAuth, React UI, third-party integrations, templates).

io.github.daedalus/mcp-smart-proxy

In its own words, on Official MCP Registry:

An MCP server that provides a smart proxy to other mcp servers

How to run each

Val Town As a Claude Code plugin

Claude Code
/plugin install valtown@claude-plugins-official

io.github.daedalus/mcp-smart-proxy As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-smart-proxy -- uvx mcp-smart-proxy

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

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: Val Town · What it can do: io.github.daedalus/mcp-smart-proxy · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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