Ext Ops Panel
Open dashboard
Comparison

dev.mcphost/mcphost vs dev.toolc/toolc

dev.mcphost/mcphost is an MCP server published by mcphost.dev. Marketplaces we read that list it: 1 (Official MCP Registry). dev.toolc/toolc is an MCP server published by toolc.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacedev.mcphost/mcphostdev.toolc/toolc
Official MCP Registry Listed
Version: 0.107.95
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 237
Downloads/week (npm): 38
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

dev.mcphost/mcphost vs dev.toolc/toolc
Factdev.mcphost/mcphostdev.toolc/toolc
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (mcphost.dev/mcp)On your machine (@toolc/cli)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/j0yen/mcphostgithub.com/toolc-dev/toolc
Changes in the last 7 days (differs)20 or more0
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

dev.mcphost/mcphost

In its own words, on Official MCP Registry:

Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.

dev.toolc/toolc

In its own words, on Official MCP Registry:

Optimizing compiler for agent tools: many MCP servers or REST APIs in, one lean endpoint out.

How to run each

dev.mcphost/mcphost As a remote MCP server

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

dev.toolc/toolc As a local MCP server: npm package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio toolc -- npx -y @toolc/cli serve

Requires: ANTHROPIC_API_KEY (secret)

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

The marketplaces of dev.mcphost/mcphost publish no settings it asks for, so we do not compare settings.

What it can do: dev.mcphost/mcphost · What it can do: dev.toolc/toolc · 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