io.github.Incultnitollc/mcp-probe vs io.github.veldica/publishready
io.github.Incultnitollc/mcp-probe is an MCP server published by Incultnitollc. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.veldica/publishready is an MCP server published by veldica. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  io.github.Incultnitollc/mcp-probe |  io.github.veldica/publishready |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Downloads/month (npm): 156 Downloads/week (npm): 26 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.0.5 Downloads/month (npm): 174 Downloads/week (npm): 23 Forks (GitHub): 1 Stars (GitHub): 2 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 | io.github.Incultnitollc/mcp-probe | io.github.veldica/publishready |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 2 | 2 |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@incultnitollc/mcp-probe) | On your machine (@veldica/publishready-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/incultnitollc/mcp-probe | github.com/veldica/publishready-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.Incultnitollc/mcp-probe
Inspect and score any MCP server 0-100 on publishability, schema and protocol before publish.
io.github.veldica/publishready
PublishReady: Deterministic writing control with local-first metrics and AI prose audits.
How to run each
io.github.Incultnitollc/mcp-probe As a local MCP server: npm package
claude mcp add --transport stdio mcp-probe -- npx -y @incultnitollc/mcp-probe serveio.github.veldica/publishready As a local MCP server: npm package
claude mcp add --transport stdio publishready -- npx -y @veldica/publishready-mcpCommands 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: io.github.Incultnitollc/mcp-probe · What it can do: io.github.veldica/publishready · 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.