fx-mcp vs io.github.jmshinhwa/mcp-2026-migration-lint
fx-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
fx-mcp is a plugin bundle for AI coding tools published by fx. No marketplace we read lists it any more. io.github.jmshinhwa/mcp-2026-migration-lint is an MCP server published by jmshinhwa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| Community marketplace fx/cc | Removed on 2026-10-24 Version: 1.0.2 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.5 Downloads/month (npm): 620 Downloads/week (npm): 38 Forks (GitHub): 1 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 | fx-mcpno longer listed · | io.github.jmshinhwa/mcp-2026-migration-lint |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 9 | 1 |
| Forks (GitHub) (differs) | 2 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@readystack/mcp-2026-migration-lint) |
| 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 | Not stated | Not stated |
| Repository (differs) | github.com/fx/cc | github.com/jmshinhwa/readystack-themes |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 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 fx-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Complete toolkit for building Model Context Protocol (MCP) servers in Go using the official github.com/modelcontextprotocol/go-sdk. Includes instructions for best practices, a…
-
High-performance, modular MCP v2 server with safe profiles, worker pool, caching, and stdio.
-
MCP server for developers documentation, generated by doc2mcp.
-
Get accurate answers about mctx and MCP servers from live docs, not outdated training data. Look up
-
Manage MCP servers - discover, analyze, execute tools/prompts/resources. Use for MCP integrations, capability discovery, tool filtering, programmatic execution, or encountering…
-
Complete toolkit for building Model Context Protocol (MCP) servers in TypeScript/Node.js using the official SDK. Includes instructions for best practices, a prompt for generating…
What each says it does
fx-mcp
MCP (Model Context Protocol) server management guidance and best practices
io.github.jmshinhwa/mcp-2026-migration-lint
The 2026-07-28 MCP revision removed the initialize handshake, sessions, ping and 4 more RPCs. 27 rul
How to run each
fx-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.jmshinhwa/mcp-2026-migration-lint As a local MCP server: npm package
claude mcp add --transport stdio mcp-2026-migration-lint -- npx -y @readystack/mcp-2026-migration-lint --mcp
Commands 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: fx-mcp · What it can do: io.github.jmshinhwa/mcp-2026-migration-lint · 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.