Aayat AI

Check a token: is it a scam? ($0.02)

token-safety

Read-only

Is this token safe to buy? Honeypot and sell-tax test, holder concentration, liquidity and locks, mint/freeze powers, proxy/upgradeable contract, with a 0-100 safety score and plain-English flags. ★ One of our best tools. Rug-pull and scam check for any token on Base, Solana, Ethereum, BNB, Arbitrum, Polygon, Optimism or Avalanche. Checks honeypot, buy/sell tax, mint/freeze authority, hidden owner, proxy, blacklist, holder concentration, locked liquidity, pool age and market data, then gives flags, a 0-100 safety score and a verdict. Price: $0.02 in USDC per call (x402 or prepaid credits). In the free trial.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	Blockchain: base, solana, ethereum, bsc, arbitrum, polygon, optimism, avalanche.	base
`address`	Yes	Token contract address (0x...) or Solana mint address.

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes
`flags`	Yes
`score`	Yes	100 = no issues found. null when the contract scan or liquidity data was unavailable (verdict 'unknown').
`market`	Yes
`address`	Yes
`holders`	Yes
`sources`	No
`verdict`	Yes
`contract`	No	Raw contract findings from the scanner.
`checkedAt`	No
`liquidity`	Yes
`disclaimer`	No
`checksNotRun`	No	Checks that couldn't run (data source blocked, empty or not covered).
`dataComplete`	No	false when some checks couldn't run; see checksNotRun.
`verdictReason`	No	Why: red flags found, which checks couldn't run, or insufficient data.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 28, 2026

addedOutput schema / properties / checksNotRun

Added value: +{
+  "description": "Checks that couldn't run (data source blocked, empty or not covered).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / dataComplete

Added value: +{
+  "description": "false when some checks couldn't run; see checksNotRun.",
+  "type": "boolean"
+}

changedOutput schema / properties / score / description

Previous value: -"100 = no issues found."New value: +"100 = no issues found. null when the contract scan or liquidity data was unavailable (verdict 'unknown')."

changedOutput schema / properties / score / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

addedOutput schema / properties / verdictReason

Added value: +{
+  "description": "Why: red flags found, which checks couldn't run, or insufficient data.",
+  "type": "string"
+}

First observedSep 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/open-world semantics, but the description adds material context they cannot: the $0.02 USDC per-call price with x402 or prepaid credits, availability in the free trial, and the full checklist of what is analyzed. It does not disclose rate limits or latency, but the billing and coverage disclosure is genuinely additive.

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

Conciseness3/5

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

Front-loaded with the core question and score output, but the check list and the chain list each appear twice ('honeypot and sell-tax test' then 'Checks honeypot, buy/sell tax...'; the eight chains are enumerated twice), which is redundant padding in an otherwise short description.

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?

An output schema exists, so return values need not be explained. The description supplies the supported chains, the checks performed, the pricing model and the trial availability, which is enough for correct invocation. The only real gap is routing guidance against the many sibling token/trade tools.

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%, so both parameters (address, chain enum) are already fully documented. The description repeats the chain list verbatim from the enum and adds no format or edge-case guidance beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Rug-pull and scam check for any token') with the exact scope of the analysis (honeypot, sell-tax, holder concentration, liquidity, mint/freeze, proxy) and the output form (0-100 score + flags + verdict). An agent can distinguish it from siblings like token-report or trade-precheck without opening any schema.

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?

The opening question 'Is this token safe to buy?' implies a pre-purchase screening use case, and the supported chains are listed. However, with many overlapping siblings (trade-precheck, trade-precheck-deep, token-report, token-report-deep, token-holders), the description never says when to pick this tool over those alternatives or when it is not appropriate.

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

All Aayat AI tools Inspect

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

Need Help?