# maiga_kol_analysis

Analyzes the influence and statistics of cryptocurrency influencers on X (Twitter)

Agent View of the PolicyLayer registry record for `maiga_kol_analysis`. HTML page: https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-kol-analysis

## Facts

- Tool: `maiga_kol_analysis`
- 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 |
| --- | --- | --- | --- |
| `username` | string | no | Twitter username (without @) of the KOL to analyze |

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_kol_analysis",
    "arguments": {}
  }
}
```

## Why maiga_kol_analysis is rated Low

This tool performs purely informational analysis of public social media metrics and influencer statistics. It has no side effects, does not execute code or commands, does not create or modify any data, and does not move funds or create financial obligations. The action is read-only querying of public data, making it a low-severity Read operation.

From the tool's own definition: "The tool 'maiga_kol_analysis' explicitly 'analyzes the influence and statistics of cryptocurrency influencers on X (Twitter)' — it retrieves and queries publicly available social media data about influencers without modifying, executing, or affecting any…"

## Use case

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

## Other tools on Maiga (5)

- `maiga_analyse_token` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-analyse-token.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