fws-client-discovery vs SERPpro
fws-client-discovery is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
fws-client-discovery is a plugin bundle for AI coding tools published by Flying Web Solutions. No marketplace we read lists it any more. SERPpro is an MCP server published by serppro.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  SERPpro | |
|---|---|---|
| Community marketplace flyingwebie/skills | Removed on 2026-10-26 Version: 1.2.1 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 No figure published 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 | fws-client-discoveryno longer listed · | SERPpro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 10 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.serppro.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 23 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/flyingwebie/skills | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (2 days 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 fws-client-discovery
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
A comprehensive registry of 28+ Go-To-Market, Technical Marketing, and Growth Automation skills. This plugin empowers Claude with specialized, pre-configured capabilities for SEO…
-
An entire marketing department as one Claude skill. 14 modules: audits scored 0-100, an 18-tactic hook engine, copy graded before you see it, ad diagnosis, GEO, email, launches…
-
Open-source AI skills for SEO, marketing, and business operations in Claude Code and Codex. Installs the complete pack, including code review, app delivery, and creator workflows.
-
Content marketing strategy, web research, and information synthesis for marketing operations
-
Content marketing strategy, web research, and information synthesis for marketing operations
-
Agentic SEO Skills with project brains, DataForSEO workflows, content, and technical SEO.
What each says it does
fws-client-discovery
Complete client discovery workflow — sitemap audit, competitor research, buyer personas, keyword strategy, and production-ready website copy with a 90-day content plan
SERPpro
Competitor backlink gaps, page-by-page link plans, publisher matches and link monitoring.
How to run each
fws-client-discovery
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SERPpro As a remote MCP server
claude mcp add --transport http serppro https://api.serppro.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SERPpro 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: fws-client-discovery · What it can do: SERPpro · 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.