Google Search Console vs Proofpoint
Google Search Console is an MCP server published by AKzar1el. Marketplaces we read that list it: 1 (Official MCP Registry). Proofpoint is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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 |  Google Search Console |  Proofpoint |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.41-registry.1 Downloads/month (npm): 1 994 Downloads/week (npm): 154 Forks (GitHub): 2 Stars (GitHub): 8 Not marked · First seen |
Listed Version: 1.1.6 Forks (GitHub): 5 Stars (GitHub): 6 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 | Google Search Console | Proofpoint |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 2 (worse) | 5 (better) |
| Last release (differs) | 2026-11-11 (better) | 2026-10-14 (worse) |
| Where it runs (differs) | On your machine (@digestseo/mcp-gsc) | On your machine (ghcr.io/wyre-ai/proofpoint-mcp:v1.1.6) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 2 | 6, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/akzar1el/mcp-gsc | github.com/wyre-ai/proofpoint-mcp |
| Changes in the last 7 days (differs) | 2 | 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
Google Search Console
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.
Proofpoint
MCP server for Proofpoint TAP — threat intelligence, forensics, quarantine, and email security.
How to run each
Google Search Console
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), TOKEN_ENCRYPTION_KEY (secret)
Proofpoint As a local MCP server: Docker image
claude mcp add --env "PROOFPOINT_SERVICE_PRINCIPAL=<YOUR_PROOFPOINT_SERVICE_PRINCIPAL>" --env "PROOFPOINT_SERVICE_SECRET=<YOUR_PROOFPOINT_SERVICE_SECRET>" --transport stdio proofpoint-mcp -- docker run -i --rm -e PROOFPOINT_SERVICE_PRINCIPAL -e PROOFPOINT_SERVICE_SECRET ghcr.io/wyre-ai/proofpoint-mcp:v1.1.6Requires: PROOFPOINT_SERVICE_PRINCIPAL, PROOFPOINT_SERVICE_SECRET (secret)
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
Only Google Search Console asks for
GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET (secret)GSC_ACCESS_MODEMCP_GSC_STATE_DIRPORTTOKEN_ENCRYPTION_KEY (secret)
Only Proofpoint asks for
AUTH_MODELOG_LEVELMCP_TRANSPORTPROOFPOINT_BASE_URLPROOFPOINT_SERVICE_PRINCIPALPROOFPOINT_SERVICE_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Google Search Console · What it can do: Proofpoint · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.