Skip to main content
Glama
Sign In

ava-genesis

by io.github.avagenesisdev
OverviewDiscussionsAdmin

Server Details

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

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A4.6/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: API key creation, template listing, simulation, gas pricing, two deployment paths (testnet vs mainnet), deployment confirmation, status polling, and token listing. Descriptions explicitly distinguish the deployment flows, preventing confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with the 'ava_' prefix (e.g., ava_confirm_deployment, ava_list_templates). The naming is predictable and self-documenting, making it easy to infer each tool's function.

Tool Count5/5

With 9 tools, the server is well-scoped for a token deployment service. Each tool addresses a specific step in the workflow (key creation, template selection, simulation, gas check, deployment, confirmation, status polling, listing) without unnecessary overhead.

Completeness5/5

The tool set covers the full lifecycle of token deployment: bootstrap (API key), planning (templates, simulation, gas prices), execution (deploy on testnet or mainnet, confirm, poll status), and auditing (list tokens). No obvious gaps for the stated purpose.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources