Ava Genesis

io.github.avagenesisdevPublished by GitHub account avagenesisdevv2.0.0Updated Oct 24, 2026

Deploy ERC-20 tokens on Ethereum, Base, BNB, Polygon via MCP. One call = deployed contract.

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Lets an assistant deploy ERC-20 token contracts on Ethereum, Base, BNB Chain, and Polygon with a single tool call.

What you can do
Ava Genesis is a remote MCP server whose stated purpose is deploying ERC-20 tokens across Ethereum, Base, BNB Chain, and Polygon. According to the registry description, one call results in a deployed contract, so the assistant can go from parameters to a live token without a manual deployment workflow. No individual tools are listed in the manifest, so the exact parameters and outputs are not documented here.
When to use it
Consider it when you want an assistant to create and deploy an ERC-20 token on one of the named chains as part of a conversation or automated flow. It is not aimed at general blockchain reading, wallet management, or non-token contract work.
Requirements
It is a remote streamable HTTP endpoint at avagenesis.com, so no local package or runtime is needed. The manifest declares no authentication, no environment variables, and no headers, but the endpoint may still require credentials or a funded wallet in practice; that is not documented in the supplied material.
Before you install
Deploying a contract is an irreversible, on-chain write that costs gas, so real funds are likely involved. The manifest declares no authentication or credentials, which is unusual for an operation that spends money and creates assets; verify who controls the deployment, which wallet pays, and what happens to the contract before using it. No tool list is provided, so the exact inputs sent to the remote service cannot be reviewed in advance.

Installation

In SourceWeft

  1. Open Ava Genesis in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.avagenesisdev%2Fava-genesis/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ava-genesis": {
      "type": "http",
      "url": "https://avagenesis.com/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.