Crypto Ledger Inspector MCP (Lighthouse Integration)

This Model Context Protocol (MCP) service acts as an interface, enabling Claude to communicate with and analyze the holdings data housed within your Lighthouse.one accounts.

Core Capabilities

• Secure Access: Establishes a protected link to Lighthouse services via transfer token URLs.
• Portfolio Summary: Provides comprehensive portfolio diagnostics, including:
• Aggregate current market valuation.
• Categorical distribution across various asset types.
• Identification of principal holdings (assets valued at $1000 USD or more).
• A registry of linked custodial accounts or wallets.
• Specific Asset Query: Retrieve in-depth data pertaining to any distinct holding within the tracked collection.
• History Retrieval: Access chronological records of all associated financial movements and transactions.
• Return on Investment (ROI) Insight: Generate analytical summaries regarding historical portfolio effectiveness and growth trajectories.

You are empowered to pose intricate, conversational inquiries regarding trends, distribution shifts, and profitability; the system will endeavor to map these requests to the appropriate underlying functions.

Integration with Claude Desktop

Prerequisite: Ensure that a recent Long-Term Support (LTS) version of Node.js is installed on your system. Utilizing tools like N-Install can streamline this setup.

To activate this capability, insert the following configuration block into your claude_desktop_config.json file:

{ "mcpServers": { "lighthouse": { "command": "npx", "args": ["-y", "mcp-lighthouse"] } } }

Following the configuration update, kindly restart the Claude application. Successful initialization will be confirmed by the absence of startup errors.

Initializing the Session (Authentication Protocol)

When prompted, you must supply the necessary authentication URL. This is obtained by executing the following sequence on the Lighthouse platform:

1. Navigate to the 'Configuration' or 'Settings' section within Lighthouse.one.
2. Select the option labeled "Link Mobile Device" or equivalent pairing mechanism.
3. Execute the action to "Copy transfer link."

This copied URI constitutes the Lighthouse transfer token URL, which the integration requires to authorize your session.

Operational Commands

Upon successful session establishment, the following operations are available for invocation via conversational input:

1. Establish Connection

Invoke the 'authenticate' function, supplying a valid Lighthouse transfer token URL to authorize access.

1. Enumerate Portfolios

Execute 'listLighthousePortfolios' to obtain a catalog of all managed portfolios and their summed valuations.

1. Retrieve Portfolio Summary

Utilize 'getLighthousePortfolio' to fetch the comprehensive, current state of your holdings, complete with granular segmentation details.

1. Access Yield Metrics

Call 'getLighthouseYieldData' to inspect accrued interest or passive income figures associated with your assets.

1. Analyze Performance Trajectory

Run 'getLighthousePerformanceData' to conduct a temporal analysis of the portfolio's financial movement.

Persistence and Session Handling

• The service preserves authentication status via a local session artifact named .lighthouse_session.
• Re-authentication is typically unnecessary unless the session is deliberately invalidated or its validity period lapses.
• Session credentials are encrypted and confined to your local execution environment.

Security Advisory: Session keys can be remotely revoked at any time via the Lighthouse administrative dashboard.

Local Security Posture

This MCP component operates strictly within your local machine's environment, interfacing directly with the Lighthouse API endpoints. Crucially, sensitive authorization data is never transmitted to the Claude model or any external service providers.

Local Deployment Instructions

1. Compile the source code:

bash npm install

npm run build

1. Integrate the server endpoint definition into the Claude application settings:

Paste the appropriate JSON configuration into the Develop settings panel, ensuring the specified paths accurately point to your compiled output file (e.g., dist/index.js).

Development Workflow

The project is constructed using TypeScript and leverages the FastMCP library for its architectural foundation. To implement modifications or augment functionality:

1. Modify the source file(s), primarily focusing on index.ts.
2. Recompile the asset bundle: npm run build.
3. Reinitialize the server process.

Prerequisites

• A functional Node.js runtime environment (version 16 or newer).
• A package manager (npm or yarn).
• An active account registered with Lighthouse.one.