# maiga_analyse_token

Performs comprehensive technical and fundamental analysis on a cryptocurrency token

Agent View of the PolicyLayer registry record for `maiga_analyse_token`. HTML page: https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-analyse-token

## Facts

- Tool: `maiga_analyse_token`
- 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: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `identifier` | string | no | Token symbol (e.g., 'bitcoin', 'ethereum', 'BTC') or contract address |

Parameters from the server's own tool schema.

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

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

## Why maiga_analyse_token is rated Low

This tool retrieves and analyzes data about cryptocurrency tokens without creating, modifying, or deleting information. It does not execute code or trigger external financial transactions.

From the tool's own definition: "Tool performs 'comprehensive technical and fundamental analysis' on cryptocurrency tokens. The description indicates data retrieval and analysis (technical analysis, fundamental analysis) with no modification, deletion, or execution of external operations."

## Use case

AI agents call maiga_analyse_token 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_analyse_token": {}
  }
}
```

## Other tools on Maiga (5)

- `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
- `maiga_trending_tokens` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-trending-tokens.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