io.github.avagenesisdev/ava-genesis vs net.postandshare/solana-token-launch
io.github.avagenesisdev/ava-genesis is an MCP server published by avagenesisdev. Marketplaces we read that list it: 1 (Official MCP Registry). net.postandshare/solana-token-launch is an MCP server published by postandshare.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.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.avagenesisdev/ava-genesis | net.postandshare/solana-token-launch |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (avagenesis.com/api/mcp) | Remote server (api.postandshare.net/mcp/solana) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-25 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (25 h ago) | not checked yet |
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.avagenesisdev/ava-genesis
Deploy ERC-20 tokens on Ethereum, Base, BNB, Polygon via MCP. One call = deployed contract.
net.postandshare/solana-token-launch
Create, launch and rug-check Solana SPL tokens over x402. Non-custodial, no keys handed over.
How to run each
io.github.avagenesisdev/ava-genesis As a remote MCP server
claude mcp add --transport http ava-genesis https://avagenesis.com/api/mcpnet.postandshare/solana-token-launch As a remote MCP server
claude mcp add --transport http solana-token-launch https://api.postandshare.net/mcp/solanaCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.avagenesisdev/ava-genesis 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.avagenesisdev/ava-genesis · What it can do: net.postandshare/solana-token-launch · 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.