# Harbor Crew Cross-Chain Report [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/Rocket-Harbor-420/harbor-cross-chain-report-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/harbor-crew-cross-chain-report

## Description
Paid read-only reports for 1–5 EVM addresses across four networks; 0.02 supported stablecoin direct.

## Tools
Capabilities this server exposes over MCP:

- **get_payment_quote**
- **submit_paid_report**

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Harbor Crew Cross-Chain Report does

Harbor Crew Cross-Chain Report MCP server connects an MCP client to the Harbor Crew report service for paid, read-only snapshots of public EVM addresses. A single report batch accepts 1–5 addresses and checks them across Ethereum, Base, Arbitrum One, and Polygon PoS.

The returned JSON records the observed block number for each supported report network, whether an EIP-7702 delegation indicator is present, contract-code size, a SHA-256 fingerprint, and an explorer link. These values describe the state observed at report time. The service is relevant to the Finance & Fintech category when an agent needs technical address evidence across several EVM networks.

## How it works

The workflow starts with a live payment quote. A customer selects a network and asset, reviews the instructions, and sends payment directly to the operator. Each batch costs 0.02 of the selected supported stablecoin. The available rails are USDC on Ethereum, Base, Arbitrum One, or Polygon; USDT on Ethereum; and Binance-Peg BSC-USD on BNB Smart Chain. BSC-USD is separate from native USDT.

After payment, the client submits the transaction hash, payer address, requested address batch, and wallet signature through the report request tool. The API requires 12 confirmations on the selected network. The signature is a `personal_sign` authorization binding the batch, payment rail, network, and transaction hash; it authorizes the report request only and cannot move funds.

Harbor Crew Cross-Chain Report does not initiate a transfer or sign a payment. When addresses are supplied to the quote tool, the authorization-message template is formatted locally rather than sending those addresses to the quote endpoint.

## Setup and configuration

Harbor Crew Cross-Chain Report is available as a hosted remote MCP endpoint and as a local dependency-free stdio server. The supplied material does not document installation commands, client-specific configuration, required environment variables, or endpoint URLs, so those details must be obtained from the repository or service operator.

Before ordering, users should have a public EVM address batch, choose one supported payment rail, and be able to provide the resulting transaction hash and wallet signature. No free preview or trial is offered.

## Tools and capabilities

- `get_payment_quote` reads current payment instructions and the live quote. It can also format the authorization-message template locally for supplied addresses.
- `submit_paid_report` sends the transaction hash, payer address, address batch, and wallet signature to request a report after payment.
- Report output includes network block numbers, EIP-7702 delegation indicators, contract-code sizes, SHA-256 fingerprints, and explorer links for requested addresses and supported networks.

## Limitations and notes

The Harbor Crew Cross-Chain Report MCP server produces point-in-time technical snapshots. It does not inspect balances or private keys, establish address ownership, determine whether delegation is malicious, prove malicious intent, or recover assets. It also does not provide a free preview or trial.

A report covers one batch of 1–5 public EVM addresses. Payment is required for every batch and goes directly to the operator. Users must verify the live quote and explicitly select the network and asset before sending funds. Native USDT should not be substituted for Binance-Peg BSC-USD on BNB Smart Chain.

_Full upstream README: https://allmcps.com/mcp/harbor-crew-cross-chain-report/readme_