TypeScript Project

Created By
EricxStonea year ago
A MCP server that works with MCP product like AAVE, Compound, etc.
Overview

What is Crypto Earn MCP?

Crypto Earn MCP is a TypeScript-based server project designed to work with decentralized finance (DeFi) products like AAVE and Compound, enabling users to earn interest on their crypto assets.

How to use Crypto Earn MCP?

To use Crypto Earn MCP, follow these steps:

  1. Install the necessary dependencies using npm install.
  2. Build the project with npm run build.
  3. Start the application using npm start.

Key features of Crypto Earn MCP?

  • Integration with popular DeFi platforms like AAVE and Compound.
  • Strict TypeScript configuration for enhanced code quality.
  • Easy setup and deployment with clear instructions.

Use cases of Crypto Earn MCP?

  1. Earning interest on crypto assets through AAVE and Compound.
  2. Developing custom DeFi applications using the MCP server.
  3. Learning and experimenting with TypeScript in a DeFi context.

FAQ from Crypto Earn MCP?

  • What are the prerequisites for using Crypto Earn MCP?

You need Node.js (v14 or later) and npm (v7 or later) or yarn installed on your machine.

  • Is Crypto Earn MCP open source?

Yes! Crypto Earn MCP is available on GitHub and can be freely used and modified.

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
EricxStone
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago