mcp-dynamic-tool-registration vs dev.mcphost/mcphost
mcp-dynamic-tool-registration is an MCP server published by jeromediaz. Marketplaces we read that list it: 1 (PyPI (MCP servers)). dev.mcphost/mcphost is an MCP server published by mcphost.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
| Marketplace |  mcp-dynamic-tool-registration |  dev.mcphost/mcphost |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.3.0 Downloads/month (PyPI): 127 Downloads/week (PyPI): 126 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.127.1 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | mcp-dynamic-tool-registration | dev.mcphost/mcphost |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-08 (worse) | 2026-11-08 (better) |
| Where it runs (differs) | On your machine (mcp-dynamic-tool-registration) | Remote server (mcphost.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jeromediaz/mcp-dynamic-tool-registration | github.com/j0yen/mcphost |
| Changes in the last 7 days (differs) | 1 | 3 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 22 h ago |
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
mcp-dynamic-tool-registration
Decorator-based, registry-first dynamic tool registration for MCP (Model Context Protocol) servers, with a bearer-token Streamable HTTP ASGI app.
dev.mcphost/mcphost
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
How to run each
mcp-dynamic-tool-registration
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
dev.mcphost/mcphost As a remote MCP server
claude mcp add --transport http mcphost https://mcphost.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only dev.mcphost/mcphost has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of mcp-dynamic-tool-registration 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: mcp-dynamic-tool-registration · What it can do: dev.mcphost/mcphost · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.