dev.toolpin/toolpin vs Keel
dev.toolpin/toolpin is an MCP server published by toolpin.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Keel is an MCP server published by seayniclabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  dev.toolpin/toolpin |  Keel |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (PyPI): 92 Downloads/week (PyPI): 31 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) 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 | dev.toolpin/toolpin | Keel |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | 0 (last published figure) |
| Forks (GitHub) (differs) | 0 | 0 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (toolpin.dev/mcp) | On your machine (keel-mcp) |
| Transport (differs) | Streamable HTTP | 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/toolpin/mcp-server | github.com/seayniclabs/sounding |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | no 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.toolpin/toolpin
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
Keel
Network diagnostics — ping, traceroute, DNS, port scanning, and connectivity testing.
How to run each
dev.toolpin/toolpin As a remote MCP server
claude mcp add --transport http toolpin https://toolpin.dev/mcpKeel As a local MCP server: PyPI package
claude mcp add --transport stdio keel -- uvx keel-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only dev.toolpin/toolpin 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: dev.toolpin/toolpin · What it can do: Keel · 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.