Skip to main content
Glama
lordbasilaiassistant-sudo

base-lp-locker-mcp

README.md
# base-lp-locker-mcp

An MCP server for AI agents to lock, manage, and withdraw LP tokens on Base. Trustless liquidity locking with time-based unlock.

## Install

```bash
npx -y base-lp-locker-mcp
```

## Tools

| Tool | Description |
|------|-------------|
| `lock_lp` | Lock LP tokens for a specified duration (handles approval automatically) |
| `get_lock` | Get lock details by lock ID |
| `get_user_locks` | Get all locks for a wallet address |
| `get_locker_info` | Get contract info, fees, and total locks |
| `withdraw_lp` | Withdraw LP tokens after lock expires |
| `extend_lock` | Extend a lock's duration |

## Setup

```json
{
  "mcpServers": {
    "base-lp-locker": {
      "command": "npx",
      "args": ["-y", "base-lp-locker-mcp"],
      "env": {
        "DEPLOYER_PRIVATE_KEY": "your-private-key"
      }
    }
  }
}
```

## Use Cases

- **Rug-proof launches**: Lock LP tokens to prove liquidity is safe
- **Vesting**: Time-lock LP positions for team or investor allocations
- **Trust**: Show holders that liquidity cannot be pulled
- **Extend**: Add more time to existing locks without withdrawing

## Fees

- **Lock fee**: 0.001 ETH per lock — goes to platform treasury
- **Gas**: ~150k gas per lock, ~80k per withdraw/extend

## Contract

- **LPLocker**: `0x32049c5B3E107737B8D00346C2241f9F21e9a154` (Base mainnet)
- **Verified on Basescan**: [View contract](https://basescan.org/address/0x32049c5B3E107737B8D00346C2241f9F21e9a154)

## License

MIT

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: locking, querying specific locks, listing user locks, checking contract info, withdrawing, and extending. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (lock_lp, get_lock, get_user_locks, get_locker_info, withdraw_lp, extend_lock).

Tool Count5/5

Six tools is well-scoped for an LP locker management server, covering core actions without unnecessary bloat.

Completeness5/5

The surface covers the full LP lock lifecycle: create (lock), read (get_lock, get_user_locks, get_locker_info), update (extend_lock), and delete/terminal action (withdraw_lp). No significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues