Zerion Api
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent with its stated purpose, but users should notice that it requires a Zerion API key and routes wallet queries through Zerion’s remote MCP service.
Before installing, confirm you trust Zerion’s remote MCP service, use a dedicated API key, and avoid submitting wallet addresses or customer/competitor research that you do not want handled by that third-party provider.
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.
Anyone configuring the skill will need to provide a Zerion API key that authorizes requests to Zerion’s service.
The skill requires a third-party API key. This is expected for Zerion API access and is disclosed, but users should treat the key as a credential and keep it scoped and revocable.
**Note**: API key required for authentication - get yours at https://developers.zerion.io
Use a dedicated Zerion API key, store it only in the intended MCP configuration, rotate it if exposed, and avoid reusing credentials across services.
Queries about wallet addresses, portfolios, transactions, or customer/competitor research may be visible to the Zerion service handling the MCP request.
The skill uses a disclosed remote MCP server, so wallet addresses and related query context may be sent to Zerion. This is aligned with the skill’s purpose, but users should understand the external data flow.
**URL**: `https://developers.zerion.io/mcp` **Type**: Remote HTTP MCP server
Only query wallet addresses you are comfortable sending to Zerion, and review Zerion’s API terms and privacy practices for sensitive business or customer research.