CryptoLabel

AI agent integration

Blockchain MCP Server for Crypto Address Labels

Connect an AI agent to maintained CryptoLabel documentation and live, read-only Bitcoin, Ethereum, and Tron address lookups.

MCP endpointhttps://cryptolabel.io/api/mcp

Purpose-built context

Let the agent inspect the source of truth

The server exposes API documentation, enum values, endpoint details, and a live address lookup as structured MCP capabilities. An agent can inspect the current contract before it answers or calls the public endpoint.

Read-only
No transaction signing, wallet connection, or state-changing blockchain operation.
Agent-ready
Structured tools replace fragile page scraping and undocumented assumptions.

Available tools

Six focused capabilities

search_docs
Search the maintained Markdown and OpenAPI documentation.
read_doc
Read a documentation resource by its MCP URI.
get_endpoint
Return endpoint details by operation ID or method and path.
check_address
Run a live Bitcoin, Ethereum, or Tron address lookup.
list_enums
Inspect current API enum values and optionally filter by schema.
list_versions
List documentation versions exposed by the server.
MCPhttps://cryptolabel.io/api/mcp

Connect CryptoLabel to an agent through MCP to search API documentation and check addresses with the live endpoint when needed. 

Settings -> Connectors -> Add custom connector
Name: CryptoLabel
URL: https://cryptolabel.io/api/mcp

Example prompts

Ask for bounded, inspectable results

Prompts should distinguish public attribution from proof of ownership and request the exact fields needed for the task.

  1. 01

    Check this Ethereum address and summarize only the attributed entity and active labels.

  2. 02

    Find the response fields returned by the address lookup endpoint.

  3. 03

    List the supported Chain enum values in the latest CryptoLabel API version.

MCP or REST

Choose the interface that matches the caller

Use MCP
When an AI agent needs discoverable tools, documentation context, and a live lookup in one connection.
Use REST
When application code already knows the endpoint and needs a direct deterministic HTTP integration.

Same data boundaries as the API

MCP returns informational entity and label context. It does not identify every wallet controller, calculate balances, assign a risk score, or authorize blockchain actions.