Slush Meme Mcp

io.github.SPIRY-ROPublished by GitHub account SPIRY-ROv2.0.1Updated Oct 27, 2026

AI-native meme coin launchpad on Avalanche. Deploy tokens, simulate trades, query risk.

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Local MCP server for an AI-native meme coin launchpad on Avalanche, letting an assistant deploy tokens, simulate trades and query risk scores.

What you can do
  • Deploy meme coin tokens through a token deployer service
  • Simulate trades before committing to them
  • Query AI-based risk scoring for tokens
  • Connect to a Hasura GraphQL backend for launchpad data
  • Run as a local stdio process, with an optional HTTP port setting
When to use it
Use it when you are working with the Avalanche meme coin launchpad and want an assistant to help deploy tokens, dry-run trades or check risk scores. It is not a general-purpose crypto or market data tool.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. Requires a Hasura GraphQL endpoint (HASURA_GRAPHQL_ENDPOINT) and admin secret (HASURA_GRAPHQL_ADMIN_SECRET), plus URLs for the risk scoring service (RISK_SCORING_URL) and token deployer service (TOKEN_DEPLOYER_URL). Optional MCP_PORT defaults to 4030. Desktop only.
Before you install
The server asks for a Hasura admin secret, which grants broad backend access; keep it scoped and out of shared logs. Token deployment and trade simulation act on real blockchain assets and may cost money or be irreversible. Requests go to third-party risk scoring and deployer services whose trustworthiness is not described.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.