hono vs io.github.mybolide/mcp-probe-kit
hono is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
hono is a plugin bundle for AI coding tools published by elct9620. No marketplace we read lists it any more. io.github.mybolide/mcp-probe-kit is an MCP server published by mybolide. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.mybolide/mcp-probe-kit | |
|---|---|---|
| Community marketplace elct9620/claudekit | Removed on 2026-10-24 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.0.0 Downloads/month (npm): 1 495 Downloads/week (npm): 181 Forks (GitHub): 5 Stars (GitHub): 39 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 4.1.1 Downloads/month (npm): 1 495 Downloads/week (npm): 181 Forks (GitHub): 5 Stars (GitHub): 39 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 | honono longer listed · | io.github.mybolide/mcp-probe-kit |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 39 |
| Forks (GitHub) (differs) | 0 | 5 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-probe-kit) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/elct9620/claude-hono-plugin | github.com/mybolide/mcp-probe-kit |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of hono
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Appwrite tools for Claude Code, including SDK skills, Appwrite MCP servers, and deployment commands.
-
💻 FAOS Developer Agent — Senior Software Engineer
-
Hologit configuration and CLI assistance
-
Bootstrap new Next.js, Flutter, and FastAPI apps with current packages, no deprecated APIs, and a consistent house style. Ships skills nextjs-app, flutter-app, and fastapi-app.
-
Enhances Claude for developing full-stack web apps with Wasp (React, Node.js, Prisma)
-
15 specialized agents and 22 skills for TypeScript fullstack development
What each says it does
hono
Provides Hono CLI skill to make agent know how to use Hono framework.
io.github.mybolide/mcp-probe-kit
Spec-driven dev workflow MCP: start_* orchestration, memory, GitNexus, quality gates.
How to run each
hono
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.mybolide/mcp-probe-kit As a local MCP server: npm package
claude mcp add --transport stdio mcp-probe-kit -- npx -y mcp-probe-kitCommands 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: hono · What it can do: io.github.mybolide/mcp-probe-kit · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.