Gate Info MCP

info_compliance_check_token_security

Read-onlyIdempotent

Public heuristic token security screen (e.g. tax/holder-risk style signals from data providers). Not a security guarantee or legal/investment advice. On-chain activity stats→get_token_onchain. Token xor address with chain; scope in schema. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Locale: en\|cn\|tw\|ja\|kr; default en.
`chain`	Yes	Chain id e.g. eth, bsc, solana, base, arb.
`scope`	No	basic (default)\|full.
`token`	No	Token symbol e.g. PEPE; xor with address.
`address`	No	Contract address; xor with token.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes
`count`	Yes
`scope`	No
`token`	No
`total`	Yes
`address`	Yes
`buy_tax`	No
`holders`	No
`sell_tax`	No
`name_risk`	No
`risk_facts`	No
`duration_ms`	Yes
`is_honeypot`	Yes
`holder_count`	No
`risk_summary`	Yes
`tax_analysis`	No
`data_analysis`	No
`low_risk_list`	No
`top10_percent`	No
`high_risk_list`	No
`is_open_source`	Yes
`middle_risk_list`	No
`dev_holding_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / data_analysis / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / data_analysis / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- addedOutput schema / properties / high_risk_list / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / high_risk_list / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / holders / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / holders / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / low_risk_list / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / low_risk_list / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / middle_risk_list / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / middle_risk_list / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / name_risk / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / name_risk / properties / sensitive_words / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / name_risk / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- changedOutput schema / properties / risk_facts / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / risk_summary / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / tax_analysis / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / tax_analysis / properties / pool_tax / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / tax_analysis / properties / pool_tax / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / tax_analysis / properties / token_tax / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / tax_analysis / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
First observedApr 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Description adds meaningful safety and limitation context beyond annotations: it states read-only public research data, no account access, no order placement or fund transfers, and that results are not a security guarantee or investment advice. These align with and reinforce the readOnly and non-destructive 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 core purpose and remains relatively compact. It uses concise shorthand and arrows for relationships, though some caveats are repeated and the 'Token xor address with chain' phrasing is slightly awkward. Overall it is efficient and 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?

Given the output schema exists and all parameters are documented, the description provides enough context: purpose, selection rules, safety characteristics, and a clear alternative for on-chain stats. The limitations and read-only nature are also covered, making it complete for an agent to decide when and how to invoke it.

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

Parameters4/5

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

Schema already covers all 5 parameters with descriptions. The description adds value by clarifying the mutual exclusivity between token and address, the requirement of chain, and pointing to scope. It does not deeply explain lang, but schema coverage is high and the added constraints improve understanding.

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?

Description clearly states it is a public heuristic token security screen with concrete examples (tax/holder-risk style signals). It distinguishes itself from on-chain activity by explicitly directing those stats to get_token_onchain, making its unique purpose unambiguous.

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?

The description provides useful usage context: it mentions token/address exclusivity, required chain, scope, and directs on-chain activity stats to a specific sibling tool. It could be more explicit about when exactly to choose this tool over others, but the alternatives and conditions are sufficiently implied.

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

All Gate Info MCP 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.