# maiga_trending_tokens

Retrieves the top trending tokens in the last 24 hours based on social media mentions and activity

Agent View of the PolicyLayer registry record for `maiga_trending_tokens`. HTML page: https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-trending-tokens

## Facts

- Tool: `maiga_trending_tokens`
- Server: Maiga (`demomagic/lucy-maiga-mcp`) — https://policylayer.com/tools/demomagic-lucy-maiga-mcp.md
- Homepage: https://github.com/demomagic/lucy-maiga-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "maiga_trending_tokens",
    "arguments": {}
  }
}
```

## Why maiga_trending_tokens is rated Low

This tool performs a read-only query operation that retrieves and aggregates publicly available social media data about cryptocurrency tokens. It has no side effects—it neither modifies data, executes code, deletes information, nor initiates financial transactions. The worst-case misuse (e.g., an agent repeatedly polling for trending data) would be a resource waste rather than a security or financial breach.

From the tool's own definition: "Tool name 'maiga_trending_tokens' and description 'Retrieves the top trending tokens' clearly indicate a data retrieval operation."

## Use case

AI agents call maiga_trending_tokens to retrieve information from Maiga without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Maiga:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "maiga_trending_tokens": {}
  }
}
```

## Other tools on Maiga (5)

- `maiga_analyse_token` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-analyse-token.md
- `maiga_kol_analysis` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-kol-analysis.md
- `maiga_market_report` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-market-report.md
- `maiga_mindshare` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-mindshare.md
- `maiga_token_info` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-token-info.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=demomagic-lucy-maiga-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/demomagic-lucy-maiga-mcp