Zerion Api

PassAudited by ClawScan on May 1, 2026.

Overview

This skill is a coherent Zerion integration for read-only crypto wallet research, but users should protect the Zerion API key and remember wallet queries go to a remote MCP service.

This appears safe for its intended read-only Zerion API use. Before installing, make sure you are comfortable configuring a Zerion API key and sending wallet addresses or portfolio-analysis questions to Zerion's remote MCP server. Do not provide seed phrases, private keys, exchange credentials, or other wallet-control secrets.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the API key is mishandled, someone else could use the user's Zerion API access or consume their quota.

Why it was flagged

The skill requires a Zerion API credential for authentication. This is expected for the stated Zerion MCP integration, but users should treat the token as sensitive and ensure it is only configured for the intended service.

Skill content
**Auth**: API key required (get at https://developers.zerion.io)
Recommendation

Use a dedicated Zerion API key, store it only in the intended MCP configuration, and rotate it if it is exposed.

What this means

Wallet addresses and portfolio-analysis requests can reveal financial research interests or link public blockchain activity to the user making the query.

Why it was flagged

The skill relies on a remote MCP server, so wallet addresses and related query details may be sent to Zerion. This is disclosed and purpose-aligned, but it is still a data-boundary consideration.

Skill content
**URL**: `https://developers.zerion.io/mcp`
**Type**: Remote HTTP MCP server
Recommendation

Only query wallet addresses you are comfortable sending to Zerion, and review Zerion's API/privacy terms before using it for sensitive customer or competitor research.