Skip to main content
Glama
pump.fun MCP Server

pump.fun MCP Server

by blixtrade

rug_check

Checks a Solana token for rug-pull risk by analyzing mint and freeze authority, Token-2022 traps, holder concentration, liquidity, and honeypot patterns, then returns a 0-100 score with findings.

Instructions

Rug pull risk check for a Solana token: mint and freeze authority, Token-2022 traps, holder concentration, liquidity, honeypot pattern. Returns a 0-100 risk score with findings.

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": "rug_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the return contract (0-100 score plus findings) and that the analysis is read-only inspection of on-chain properties. It says nothing about whether results are cached or live, how long the check takes, whether an invalid or illiquid mint causes errors or low confidence, or whether the score is comparable across tokens.

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

Conciseness5/5

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

One compact sentence front-loads the purpose, enumerates the checks, and closes with the return shape. No filler, no restatement of the tool name.

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

Completeness4/5

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

For a low-complexity read tool with one fully documented parameter and no output schema, the description supplies the missing return contract (score range plus findings), which is the main thing the schema cannot convey. Remaining gaps are minor edge-case behavior, not core invocation information.

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?

The single required parameter has 100% schema description coverage ("Solana token mint address (base58)"), so the schema does the work and the description adds no format or validation guidance beyond it. Baseline 3 for a one-parameter tool with full coverage.

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

Purpose4/5

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

"Rug pull risk check for a Solana token" gives a specific analysis verb and resource, and the enumeration of checks (mint/freeze authority, Token-2022 traps, holder concentration, liquidity, honeypot) makes it clearly distinct from generic siblings like token_info or top_holders. It stops short of naming a sibling, so an agent still has to infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the pre-trade safety screen rather than a data lookup, but the description never states when to prefer it over screen_tokens or token_info. No exclusions, prerequisites, or cost/latency cautions are given.

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