# maiga_mindshare

Analyzes social media sentiment and trending discussions about a token over the last 24 hours

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

## Facts

- Tool: `maiga_mindshare`
- 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 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_mindshare",
    "arguments": {}
  }
}
```

## Why maiga_mindshare is rated Low

This tool performs read-only operations: it queries and analyzes social media sentiment and trending discussions. It retrieves information without side effects, modifications to data, code execution, or financial impact. While the broader Maiga server involves cryptocurrency analysis that could inform trading decisions, this specific tool itself only reads and analyzes sentiment data.

From the tool's own definition: "Tool 'maiga_mindshare' analyzes social media sentiment and trending discussions—retrieval and analysis of publicly available sentiment data with no modification, deletion, execution, or financial transaction capability."

## Use case

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

## 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_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