zkLombard (@zkLombard) on X

What it claims

zkLombard has released a remote MCP server that lets an agent with its own wallet take a loan against a Uniswap v3 position. The post describes it as one endpoint with eight tools and no key held by zkLombard. The agent can value the position, pledge it, borrow USDG, repay, and redeem it. Loan solvency is proven with a zero-knowledge proof checked on chain. The agent signs every transaction itself. The post calls this the project's "first update."

How to use it

Register the server with Claude Code using the command the post gives verbatim:

claude mcp add --transport http zklombard zklombard.com/api/mcp

• Server name: zklombard
• Endpoint: zklombard.com/api/mcp
• Manual: zklombard.com/mcp

The post does not list the eight tool names, their parameters or their return shapes. Read the manual before wiring an agent to it.

The agent needs a wallet that holds its own signing key, because the server holds none. The agent also needs a Uniswap v3 position to pledge.

Limits

The post is a short announcement. It leaves out everything an engineer would need to judge the financial and security terms:

• Chain and contracts: no chain or network is named, and no contract addresses are given.
• Loan terms: there are no loan-to-value ratios, interest rates, fees, liquidation rules or USDG details.
• Proof details: nothing describes what the zero-knowledge proof attests, which proof system it uses, or who generates it.
• Auth and limits: the endpoint's authentication and rate limits are not stated.

"No key on our side" means signing responsibility, and the risk of signing a bad transaction, sits entirely with the agent's wallet. Treat this as an early release and check the manual and contracts before letting an autonomous agent pledge real assets.