Rugsight

Solana token full risk report (0.03 USDC, x402)

get_token_risk_report

Read-only

Rugsight full risk report for a Solana SPL / Token-2022 token: mint & freeze authority, Token-2022 extensions, top-20 holder breakdown (wallets vs pools/programs/burn), liquidity, 24h volume, pool age, every risk flag explained, 0-100 score and A-F grade (or IC = issuer-controlled for allowlisted regulated assets such as USDC, PYUSD, cbBTC or xStocks). Costs 0.03 USDC on Solana per call, paid with x402: call without payment to receive the PaymentRequired object, then retry with _meta["x402/payment"].

Input Schema

Name	Required	Description	Default
`mint`	Yes	Solana token mint address (base58)

Output Schema

Name	Required	Description
`mint`	Yes
`name`	No
`flags`	Yes
`grade`	Yes	A-F from the score; IC = issuer-controlled (allowlisted regulated/issuer asset)
`score`	Yes
`issuer`	No
`market`	No
`symbol`	No
`holders`	No
`verdict`	No
`decimals`	No
`supplyUi`	No
`checkedAt`	No
`confidence`	Yes
`disclaimer`	No
`extensions`	No
`tokenProgram`	No
`mintAuthority`	No
`technicalGrade`	No
`freezeAuthority`	No
`authorityHolders`	No
`issuerControlled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 31, 2026

addedOutput schema / properties / authorityHolders

Added value: +{
+  "properties": {
+    "freeze": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "mint": {
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / grade / description

Added value: +"A-F from the score; IC = issuer-controlled (allowlisted regulated/issuer asset)"

changedOutput schema / properties / grade / enum

Previous value: -[
-  "A",
-  "B",
-  "C",
-  "D",
-  "F"
-]New value: +[
+  "A",
+  "B",
+  "C",
+  "D",
+  "F",
+  "IC"
+]

addedOutput schema / properties / issuer

Added value: +{
+  "properties": {
+    "assetType": {
+      "enum": [
+        "stablecoin",
+        "tokenized-stock",
+        "wrapped-asset"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / issuerControlled
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / technicalGrade

Added value: +{
+  "enum": [
+    "A",
+    "B",
+    "C",
+    "D",
+    "F"
+  ],
+  "type": "string"
+}

First observedOct 30, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well past the annotations by disclosing the paid nature (0.03 USDC on Solana per call), the exact two-step payment handshake, and the IC = issuer-controlled special case for allowlisted regulated assets like USDC or PYUSD — a non-obvious output convention an agent could easily misread. It also enumerates the report contents so the caller knows the shape and depth of the response.

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?

Front-loaded with the payoff (full risk report) followed by the content enumeration, then the payment mechanic last. The middle enumeration is long but each item is real information an agent needs to judge whether to spend 0.03 USDC, so little is wasted.

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?

Complete for a single-parameter read tool: the output schema handles return structure, and the description still covers cost, payment retry mechanics, and the IC grade edge case. Nothing an agent needs in order to invoke it successfully is 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?

The single mint parameter is already fully documented in the schema (base58 mint address with a base58 pattern constraint), so the description adds no format or validation meaning beyond it. With 100% schema coverage this is the expected baseline rather than a gap.

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?

Names a specific verb and resource ("Rugsight full risk report for a Solana SPL / Token-2022 token") and enumerates exactly what the report contains: authorities, Token-2022 extensions, holder breakdown, liquidity, volume, pool age, flags, score and grade. It is unmistakably the comprehensive variant, though it never names or contrasts with the sibling get_token_risk_score, so the agent must infer that the sibling is the cheaper score-only path.

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?

Gives concrete operational guidance for the x402 flow: call without payment to receive the PaymentRequired object, then retry with _meta["x402/payment"]. It does not state when to prefer this over get_token_risk_score or when a full report is unnecessary, so the sibling routing decision is left implicit.

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

All Rugsight 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.