rugcheck-ai
Server Details
Solana token safety for AI agents — rug-pull, honeypot & Token-2022 trap detection before you buy.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- MrWizardlyLoaf/rugcheck-ai
- GitHub Stars
- 1
- Server Listing
- RugCheck AI
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
15 tool updates
- Added
batch_scan - Changed
check_authorities9 fields changed- added
Input schema / properties / mint / descriptionAdded value: +"The SPL or Token-2022 mint address to inspect." - changed
Output schema / descriptionPrevious value: -"Mint/freeze authority and Token-2022 extension report for a mint."New value: +"Mint/freeze authority and Token-2022 extension report for one mint." - added
Output schema / properties / dangerous_extensions / descriptionAdded value: +"Subset considered dangerous: permanentDelegate, transferHook, nonTransferable, pausable." - added
Output schema / properties / error / descriptionAdded value: +"Populated when the mint could not be read." - added
Output schema / properties / freeze_authority / descriptionAdded value: +"Active freeze-authority address, or None if revoked." - added
Output schema / properties / mint / descriptionAdded value: +"The mint address inspected." - added
Output schema / properties / mint_authority / descriptionAdded value: +"Active mint-authority address, or None if revoked." - added
Output schema / properties / token2022_extensions / descriptionAdded value: +"All Token-2022 extensions present on the mint." - added
Output schema / properties / verdict / descriptionAdded value: +"'clean' if no authorities/traps present, otherwise 'review'."
- Added
check_deployer - Added
check_liquidity - Added
compare_tokens - Changed
execute_safe_swap10 fields changed- changed
Input schema / properties / amount_usd / descriptionPrevious value: -"Amount to spend, in USD."New value: +"Amount to spend, in USD of the input token." - added
Input schema / properties / input_mintAdded value: +{ + "default": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v", + "description": "Mint to pay with — defaults to USDC. The swap is always input_mint -> mint.", + "type": "string" +} - changed
Input schema / properties / wallet / descriptionPrevious value: -"The agent's wallet (signer & funder)."New value: +"The agent's wallet — signer and funder (the swap is built for this pubkey)." - changed
Output schema / descriptionPrevious value: -"A built, unsigned swap transaction for the agent to sign."New value: +"An UNSIGNED swap transaction (or a block notice) returned for the agent to sign itself." - added
Output schema / properties / action / descriptionAdded value: +"'buy' when a swap was built, or 'blocked' when the token failed the safety screen." - added
Output schema / properties / amount_usd / descriptionAdded value: +"The USD size requested for the trade." - added
Output schema / properties / note / descriptionAdded value: +"Human-readable note: sign to execute, or why it was blocked." - added
Output schema / properties / route / descriptionAdded value: +"Route label: 'safety-verified' when screened & built, 'screen-blocked' if refused." - added
Output schema / properties / token / descriptionAdded value: +"The token mint the swap targets." - added
Output schema / properties / transaction / descriptionAdded value: +"Base64 UNSIGNED transaction for the agent to sign & submit; empty if blocked."
- Added
holders_breakdown - Added
is_safe - Added
rug_forecast - Added
scammer_dna - Added
scan_token - Changed
simulate_sell8 fields changed- added
Input schema / properties / mint / descriptionAdded value: +"The SPL or Token-2022 mint address to test for sellability." - changed
Output schema / descriptionPrevious value: -"Whether a token can be sold (honeypot check) from on-chain constraints."New value: +"Honeypot / sellability result for one mint — whether a buyer could actually sell it back." - added
Output schema / properties / blocking_extensions / descriptionAdded value: +"Extensions that block selling (nonTransferable, pausable)." - added
Output schema / properties / error / descriptionAdded value: +"Populated when the mint could not be read." - added
Output schema / properties / freeze_authority / descriptionAdded value: +"Active freeze authority, which can also block selling." - added
Output schema / properties / mint / descriptionAdded value: +"The mint address checked." - added
Output schema / properties / sellable / descriptionAdded value: +"True if a live sell route exists and nothing on-chain blocks selling; False if blocked or no route; None if it could not be determined." - added
Output schema / properties / verdict / descriptionAdded value: +"Plain-language sellability summary with the reason."
- Added
simulate_trade - Added
token_age - Changed
verify_token_safety11 fields changed- added
Input schema / properties / mint / descriptionAdded value: +"The SPL or Token-2022 mint address to audit." - changed
Output schema / descriptionPrevious value: -"Result of an on-chain token safety audit."New value: +"On-chain safety verdict for one SPL / Token-2022 mint, produced before you trade it." - added
Output schema / properties / decimals / descriptionAdded value: +"Token decimal places." - added
Output schema / properties / error / descriptionAdded value: +"Populated when the mint could not be read." - added
Output schema / properties / extensions / descriptionAdded value: +"Token-2022 extensions present on the mint (e.g. transferHook)." - added
Output schema / properties / freeze_authority / descriptionAdded value: +"Active freeze-authority address if present — its holder can freeze your account so you cannot sell; None means revoked." - added
Output schema / properties / mint_authority / descriptionAdded value: +"Active mint-authority address if present — its holder can mint new supply and dilute you after purchase; None means revoked." - added
Output schema / properties / risks / descriptionAdded value: +"Plain-language risk flags detected; empty means none found." - added
Output schema / properties / supply / descriptionAdded value: +"Raw on-chain total supply." - added
Output schema / properties / token / descriptionAdded value: +"The mint address that was audited." - added
Output schema / properties / verdict / descriptionAdded value: +"Overall risk: SAFE (no red flags), CAUTION (authority/liquidity risk), DANGER (rug or honeypot trap present), or UNKNOWN (not a mint / RPC unavailable)."
1 tool update
- Changed
execute_safe_swap12 fields changed- removed
Input schema / properties / amountRemoved value: -{ - "description": "Amount of `input_mint` to swap, in human units (e.g. 50 = 50 USDC).", - "type": "number" -} - added
Input schema / properties / amount_usdAdded value: +{ + "description": "Amount to spend, in USD.", + "type": "number" +} - removed
Input schema / properties / input_mintRemoved value: -{ - "description": "The token you pay with.", - "type": "string" -} - added
Input schema / properties / mintAdded value: +{ + "description": "Token to buy.", + "type": "string" +} - removed
Input schema / properties / output_mintRemoved value: -{ - "description": "The token you want to receive.", - "type": "string" -} - changed
Input schema / requiredPrevious value: -[ - "input_mint", - "output_mint", - "wallet", - "amount" -]New value: +[ + "mint", + "wallet", + "amount_usd" +] - removed
Output schema / properties / amountRemoved value: -{ - "type": "number" -} - added
Output schema / properties / amount_usdAdded value: +{ + "type": "number" +} - removed
Output schema / properties / input_mintRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / output_mintRemoved value: -{ - "type": "string" -} - added
Output schema / properties / tokenAdded value: +{ + "type": "string" +} - changed
Output schema / requiredPrevious value: -[ - "action", - "input_mint", - "output_mint", - "amount", - "route", - "note", - "transaction" -]New value: +[ + "action", + "token", + "amount_usd", + "route", + "note", + "transaction" +]
1 tool update
- Changed
execute_safe_swap12 fields changed- added
Input schema / properties / amountAdded value: +{ + "description": "Amount of `input_mint` to swap, in human units (e.g. 50 = 50 USDC).", + "type": "number" +} - removed
Input schema / properties / amount_usdRemoved value: -{ - "description": "Amount to spend, in USD.", - "type": "number" -} - added
Input schema / properties / input_mintAdded value: +{ + "description": "The token you pay with.", + "type": "string" +} - removed
Input schema / properties / mintRemoved value: -{ - "description": "Token to buy.", - "type": "string" -} - added
Input schema / properties / output_mintAdded value: +{ + "description": "The token you want to receive.", + "type": "string" +} - changed
Input schema / requiredPrevious value: -[ - "mint", - "wallet", - "amount_usd" -]New value: +[ + "input_mint", + "output_mint", + "wallet", + "amount" +] - added
Output schema / properties / amountAdded value: +{ + "type": "number" +} - removed
Output schema / properties / amount_usdRemoved value: -{ - "type": "number" -} - added
Output schema / properties / input_mintAdded value: +{ + "type": "string" +} - added
Output schema / properties / output_mintAdded value: +{ + "type": "string" +} - removed
Output schema / properties / tokenRemoved value: -{ - "type": "string" -} - changed
Output schema / requiredPrevious value: -[ - "action", - "token", - "amount_usd", - "route", - "note", - "transaction" -]New value: +[ + "action", + "input_mint", + "output_mint", + "amount", + "route", + "note", + "transaction" +]
4 tool updates
- Changed
check_authorities1 field changed- removed
Input schema / properties / mint / descriptionRemoved value: -"The Solana token mint address (base58) to inspect."
- Changed
execute_safe_swap4 fields changed- changed
Input schema / properties / amount_usd / descriptionPrevious value: -"Amount to spend on the buy, in US dollars."New value: +"Amount to spend, in USD." - removed
Input schema / properties / amount_usd / exclusiveMinimumRemoved value: -0 - changed
Input schema / properties / mint / descriptionPrevious value: -"The Solana token mint address (base58) to inspect."New value: +"Token to buy." - changed
Input schema / properties / wallet / descriptionPrevious value: -"The agent's wallet address (base58) — signer and funder."New value: +"The agent's wallet (signer & funder)."
- Changed
simulate_sell1 field changed- removed
Input schema / properties / mint / descriptionRemoved value: -"The Solana token mint address (base58) to inspect."
- Changed
verify_token_safety1 field changed- removed
Input schema / properties / mint / descriptionRemoved value: -"The Solana token mint address (base58) to inspect."
4 tool updates
- Changed
check_authorities1 field changed- added
Input schema / properties / mint / descriptionAdded value: +"The Solana token mint address (base58) to inspect."
- Changed
execute_safe_swap4 fields changed- changed
Input schema / properties / amount_usd / descriptionPrevious value: -"Amount to spend, in USD."New value: +"Amount to spend on the buy, in US dollars." - added
Input schema / properties / amount_usd / exclusiveMinimumAdded value: +0 - changed
Input schema / properties / mint / descriptionPrevious value: -"Token to buy."New value: +"The Solana token mint address (base58) to inspect." - changed
Input schema / properties / wallet / descriptionPrevious value: -"The agent's wallet (signer & funder)."New value: +"The agent's wallet address (base58) — signer and funder."
- Changed
simulate_sell1 field changed- added
Input schema / properties / mint / descriptionAdded value: +"The Solana token mint address (base58) to inspect."
- Changed
verify_token_safety1 field changed- added
Input schema / properties / mint / descriptionAdded value: +"The Solana token mint address (base58) to inspect."
4 tool updates
- Changed
check_authorities4 fields changed- removed
Output schema / additionalPropertiesRemoved value: -true - added
Output schema / descriptionAdded value: +"Mint/freeze authority and Token-2022 extension report for a mint." - added
Output schema / propertiesAdded value: +{ + "dangerous_extensions": { + "default": [], + "items": { + "type": "string" + }, + "type": "array" + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "freeze_authority": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "mint": { + "type": "string" + }, + "mint_authority": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "token2022_extensions": { + "default": [], + "items": { + "type": "string" + }, + "type": "array" + }, + "verdict": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + } +} - added
Output schema / requiredAdded value: +[ + "mint" +]
- Changed
execute_safe_swap4 fields changed- removed
Output schema / additionalPropertiesRemoved value: -true - added
Output schema / descriptionAdded value: +"A built, unsigned swap transaction for the agent to sign." - added
Output schema / propertiesAdded value: +{ + "action": { + "type": "string" + }, + "amount_usd": { + "type": "number" + }, + "note": { + "type": "string" + }, + "route": { + "type": "string" + }, + "token": { + "type": "string" + }, + "transaction": { + "type": "string" + } +} - added
Output schema / requiredAdded value: +[ + "action", + "token", + "amount_usd", + "route", + "note", + "transaction" +]
- Changed
simulate_sell4 fields changed- removed
Output schema / additionalPropertiesRemoved value: -true - added
Output schema / descriptionAdded value: +"Whether a token can be sold (honeypot check) from on-chain constraints." - added
Output schema / propertiesAdded value: +{ + "blocking_extensions": { + "default": [], + "items": { + "type": "string" + }, + "type": "array" + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "freeze_authority": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "mint": { + "type": "string" + }, + "sellable": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ], + "default": null + }, + "verdict": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + } +} - added
Output schema / requiredAdded value: +[ + "mint" +]
- Changed
verify_token_safety4 fields changed- removed
Output schema / additionalPropertiesRemoved value: -true - added
Output schema / descriptionAdded value: +"Result of an on-chain token safety audit." - added
Output schema / propertiesAdded value: +{ + "decimals": { + "anyOf": [ + { + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "extensions": { + "default": [], + "items": { + "type": "string" + }, + "type": "array" + }, + "freeze_authority": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "mint_authority": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "risks": { + "default": [], + "items": { + "type": "string" + }, + "type": "array" + }, + "supply": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "token": { + "type": "string" + }, + "verdict": { + "type": "string" + } +} - added
Output schema / requiredAdded value: +[ + "token", + "verdict" +]
4 tool updates
- First observed
check_authorities - First observed
execute_safe_swap - First observed
simulate_sell - First observed
verify_token_safety
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Solana pre-trade safety for agents: rug check, honeypot sell-sim, drainer scan, tx preflight.
Pre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy.
31Solana pre-trade safety for AI agents: cabal, bundle, dump, deployer & honeypot in one verdict.
RiskDataApi — Solana token risk scoring for AI agents. Safety score, insider clusters, honeypot.
31
Related MCP Servers
- FlicenseBqualityCmaintenanceEnables AI agents to perform token security audits, honeypot detection, liquidity analysis, and risk scoring to avoid crypto scams.1-

SolSentry MCPofficial
AlicenseAqualityBmaintenanceProvides post-deploy Solana threat intelligence, enabling AI agents to check operators, tokens, and network stats for detecting rug pulls and malicious activity.527MIT- AlicenseAqualityBmaintenanceOn-chain Solana token safety for trading agents — traces coordinated wallet funding, same-block Jito bundles, serial-rug deployers and live coordinated dumps into one Exit-Liquidity Risk verdict before a swap. Free tier, then $0.02 USDC/query via x402.1431MIT
- AlicenseNot gradedqualityAmaintenanceOn-chain Solana token safety MCP — screens SPL / Token-2022 tokens for rug-pull and honeypot patterns (mint/freeze authority, liquidity, holders, sellability), then executes MEV-protected swaps.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Several tools overlap in purpose, particularly scan_token and verify_token_safety both offering a full safety verdict. Tools like is_safe, batch_scan, and compare_tokens also reuse aspects of the core scan, creating ambiguity about which to use for a given task.
Tool names are inconsistent in style: some use verb_noun (scan_token, simulate_sell), others are noun phrases (holders_breakdown, rug_forecast) or mixed (verify_token_safety, execute_safe_swap). Underscores are used sporadically, and names like 'scammer_dna' lack clarity.
With 15 tools focused on token safety analysis, the count is appropriate for covering various aspects without being overwhelming. The scope is well-defined, and each tool addresses a specific need, though some consolidation could reduce redundancy.
The server covers the full lifecycle of token safety analysis: scanning, specific checks (authorities, liquidity, holders), simulation, comparison, and forecasting. Minor gaps exist (e.g., no tool for retrieving basic token metadata), but the core safety workflow is well-supported.