mcp-tools vs Ieee Standards
mcp-tools is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑02.
mcp-tools is a plugin bundle for AI coding tools published by izumin5210. No marketplace we read lists it any more. Ieee Standards is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  Ieee Standards | |
|---|---|---|
| Community marketplace izumin5210/dotfiles | Removed on 2026-11-02 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 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
| Fact | mcp-toolsno longer listed · | Ieee Standards |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 22 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | Remote server (mcp.deepwiki.com/mcp) | Remote server (gateway.pipeworx.io/ieee-standards/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/izumin5210/dotfiles | github.com/pipeworx-io/mcp-ieee-standards |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 7 h ago |
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 mcp-tools
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
guru-mcp io.github.mrfentmen/guru-mcp
Guru knowledge base search and collections.
-
mcp io.minnas/mcp
Share prompts and context with your team and discover community collections.
-
Build high-quality MCP servers for LLM integrations
-
Git content governance, 23 deterministic MCP tools. Hosted: docs.contentrain.io/developer/mcp-cloud
-
Source-grounded Quickshell, QML, and Qt documentation, examples, and real-world implementations.
-
Curated knowledge for AI agents — 19K chunks, 121 skills, semantic search via MCP
What each says it does
mcp-tools
Personal MCP servers (any-script-mcp, o3-search, deepwiki)
Ieee Standards
IEEE Xplore MCP — BYOK wrapper over the IEEE Xplore Metadata Search API…
How to run each
mcp-tools
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Ieee Standards As a remote MCP server
claude mcp add --transport http ieee-standards https://gateway.pipeworx.io/ieee-standards/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Ieee Standards 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
Only mcp-tools asks for
OPENAI_API_KEY (secret)OPENAI_API_TIMEOUTREASONING_EFFORTSEARCH_CONTEXT_SIZE
Only Ieee Standards asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: mcp-tools · What it can do: Ieee Standards · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.