io.github.Explorer-64/stackapps-suite-mcp vs io.github.VestOSAI/vest-mcp
io.github.Explorer-64/stackapps-suite-mcp is an MCP server published by Explorer-64. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.VestOSAI/vest-mcp is an MCP server published by VestOSAI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  io.github.Explorer-64/stackapps-suite-mcp |  io.github.VestOSAI/vest-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.10 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.0.0 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 | io.github.Explorer-64/stackapps-suite-mcp | io.github.VestOSAI/vest-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Not stated | Remote server (mcp.getvest.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| 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/explorer-64/stackapps | github.com/vestosai/vest-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 39 h ago |
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
io.github.Explorer-64/stackapps-suite-mcp
StackApps suite gateway: Imagcon, StackBill, Dicta-Notes. Pay per call in USDC via x402.
io.github.VestOSAI/vest-mcp
Earn up to 20% cashback on 200+ AI tool subscriptions. Browse, build stacks, get tracked links.
How to run each
io.github.Explorer-64/stackapps-suite-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.VestOSAI/vest-mcp As a remote MCP server
claude mcp add --transport http vest-mcp https://mcp.getvest.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.VestOSAI/vest-mcp 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: io.github.Explorer-64/stackapps-suite-mcp · What it can do: io.github.VestOSAI/vest-mcp · 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.