Ext Ops Panel
Open dashboard
Comparison

io.github.Deesmo/arch-tools-mcp vs toolsmelt

io.github.Deesmo/arch-tools-mcp is an MCP server published by Deesmo. Marketplaces we read that list it: 1 (Official MCP Registry). toolsmelt is an MCP server published by sepehr071. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplaceio.github.Deesmo/arch-tools-mcptoolsmelt
Official MCP Registry Listed
Version: 2.0.1
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.8.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

io.github.Deesmo/arch-tools-mcp vs toolsmelt
Factio.github.Deesmo/arch-tools-mcptoolsmelt
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-22
Where it runs (differs)Remote server (archtools.dev/mcp)On your machine (toolsmelt)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/deesmo/arch-ai-toolsgithub.com/sepehr071/toolsmelt
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-22
Endpoint at the last check (differs)Responded 6 days agono 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

io.github.Deesmo/arch-tools-mcp

In its own words, on Official MCP Registry:

63 production tools for AI agents — one API key, pay per call in USDC (x402) or Stripe credits.

toolsmelt

In its own words, on Official MCP Registry:

Curated MCP tools from OpenAPI, websites, apps, Postman, cURL or SQL; your agent designs them.

How to run each

io.github.Deesmo/arch-tools-mcp As a remote MCP server

Claude Code
claude mcp add --transport http arch-tools-mcp https://archtools.dev/mcp

toolsmelt As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio toolsmelt -- uvx toolsmelt mcp

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

Only io.github.Deesmo/arch-tools-mcp 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: io.github.Deesmo/arch-tools-mcp · What it can do: toolsmelt · Compare two other plugins

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