Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Solana token rug check / safety scan

solana_token_rug_check
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Rug-pull and safety check for any Solana SPL or Token-2022 mint (pump.fun memecoins included). Shows whether mint authority and freeze authority are revoked, supply and decimals, top-10 holder concentration, token age, metadata mutability, liquidity, and pump.fun bonding-curve or graduated status. Returns a 0-100 risk score with plain-English red flags. Not financial advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mint": "<mint>"
    },
    "name": "solana_token_rug_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58), e.g. 9uSa1csCpzfm76Ms2sPnwWn78XUKJE86ND1VobqHpump

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds valuable operational context: it is free, requires no API key, and has an approximate 100 calls/day limit. It also discloses the main outputs (risk score, plain-English red flags, authority status, holder concentration, liquidity, pump.fun status) and includes a not-financial-advice disclaimer. This is substantial transparency beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the most actionable facts: free, no API key, and the core safety-check purpose. The subsequent sentences efficiently list checked attributes and the return format. It is appropriately sized for the tool's scope, though the attribute list is dense and could have been slightly more scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description explains the key return value: a 0-100 risk score plus plain-English red flags and specific checked fields. Annotations cover the read-only, idempotent, open-world behavior, and the description adds rate-limit and authentication context. Nothing critical for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already defines the single mint parameter as a base58 Solana token mint address with an example. The description reinforces that the parameter accepts SPL and Token-2022 mints, including pump.fun tokens, but adds only marginal parameter-specific meaning. Baseline 3 is appropriate when the schema already carries the parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: a rug-pull and safety check for any Solana SPL or Token-2022 mint, including pump.fun tokens. This clearly distinguishes it from sibling tools such as swap quote, ticker availability, or vibe scoring. The scope is explicit enough that an agent can identify the tool's core function without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the usage context: safety-checking any Solana SPL or Token-2022 mint, with pump.fun memecoins explicitly included. However, it does not explicitly name when to use this tool versus a sibling like memecoin_vibe_check_score, nor does it state exclusions. The guidance is clear but not fully comparative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources