Which integrations are available for this server?

Provides tools for browsing, quoting, and optionally transacting with FlashBank P2P term-loan escrow and flash-loan router contracts on Ethereum and its testnets.

FlashBank MCP server

A Model Context Protocol server that lets AI agents browse, quote and (optionally) transact with the FlashBank contracts — the P2P term-loan escrow and the flash-loan router — on Ethereum, Base, Arbitrum and the Sepolia playground.

Self-contained: inline minimal ABIs, public RPCs, no Hardhat compilation needed. Read tools work with zero configuration; write tools are opt-in and safety-gated.

cd mcp && npm install && npm test     # 16 tests incl. a full MCP stdio handshake — no network/key needed
npm run smoke                         # live read-only check against the deployed contracts
npm run drill                         # LIVE two-agent lifecycle drill on Sepolia (needs a funded key)

The drill spawns two real MCP server instances (lender agent + a throwaway borrower agent) and walks faucet → create → browse → take (pinned) → early repay (cooling-off rebate verified) → withdraw-unclaimed probe → cancel, with real transactions on the Sepolia playground.

Safety model

Mode	Requirement	What it allows
Read-only (default)	nothing	browse offers, quotes, pool stats, wallet lookups
Playground writes	`FLASHBANK_MCP_PRIVATE_KEY`	create/take/repay/claim/cancel + faucet on Sepolia
Mainnet writes	…and `FLASHBANK_MCP_ALLOW_MAINNET=true`	the same on Ethereum/Base — real assets, real risk

Use a dedicated throwaway key for agents; never a key holding meaningful funds. Mainnet writes are deliberately double-gated and the contracts carry no external audit.

Related MCP server: Base MCP Server

Tools

Read (always available)

Tool	Purpose
`explain`	Plain-English primer on both products — agents should call this first
`list_chains`	Chains, contract addresses, registry tokens, current write permissions
`wallet_status`	Signer address + native/token balances on a chain
`p2p_list_offers`	Open offers, boosted first, with human-readable terms
`p2p_get_loan`	Full detail: terms, take quote, repayment quote, default split, terms pin
`p2p_my_loans`	Loans created by an address (or the signing wallet)
`flash_pools`	Flash-loan liquidity, fee bps, caps and provider count per token
`flash_quote`	Fee + fundability quote for a flash-borrow amount

Write (gated as above)

Tool	Purpose
`p2p_create_offer`	Post a lend offer / borrow request (escrows your side; handles the approval; optional `coolingOffHours` on v2 chains)
`p2p_take_offer`	Accept an offer, pinning the exact reviewed terms on-chain (terms hash, or version pin on older builds — feature-detected)
`p2p_repay`	Repay and redeem collateral; on v2 chains reports the vested fee and any cooling-off rebate
`p2p_claim_default`	Lender claims collateral after the repay window closes
`p2p_cancel`	Cancel your untaken offer and reclaim escrow
`p2p_withdraw_unclaimed`	v2: withdraw a payout that queued because it couldn't be delivered to you
`faucet_mint`	Mint 10,000 fpUSD/fpETH play-money (Sepolia only)

Flash loans are quote/read only by design: executing one requires a smart contract implementing the borrower callback, which is not something an MCP tool should improvise.

Using it from Cursor

The repo ships a project-level .cursor/mcp.json that registers this server in read-only mode. To enable writes, add env vars (throwaway key!):

{
	"mcpServers": {
		"flashbank": {
			"command": "node",
			"args": ["mcp/src/server.js"],
			"env": {
				"FLASHBANK_MCP_PRIVATE_KEY": "0x<throwaway-key-funded-on-sepolia>"
			}
		}
	}
}

Any other MCP client works the same way — stdio transport, command node mcp/src/server.js.

Environment variables

Variable	Default	Meaning
`FLASHBANK_MCP_PRIVATE_KEY`	unset	Signing key; unset = read-only
`FLASHBANK_MCP_ALLOW_MAINNET`	unset	`true` unlocks mainnet writes
`FLASHBANK_MCP_RPC_<CHAIN>`	public RPC	Override the RPC per chain, e.g. `FLASHBANK_MCP_RPC_ETHEREUM`

Layout

src/chains.js         chain registry (addresses, tokens, RPCs, p2pVersion) — update on redeploys
src/abi.js            inline minimal ABIs, version-aware (v1 mainnets, v2 Sepolia playground)
src/clients.js        providers, signer, write gate, token resolution, allowances
src/format.js         pure formatting helpers (unit-tested)
src/server.js         the MCP server + tool definitions
scripts/mcp-client.js minimal stdio client shared by the protocol test and the drill
scripts/smoke.js      live read-only smoke against the real deployments
scripts/drill.js      live two-agent lifecycle drill on Sepolia
test/                 node:test suites incl. a full MCP stdio protocol test

The Sepolia playground runs FlashBankP2PLoanV2 (0x536f…1E76): cooling-off rebate, token validation and pull-payouts (see docs/design/P2P_V2_COOLING_OFF.md). Mainnets stay on v1 until v2 graduates.

This server cannot be installed

A

license - permissive license

-

quality - not tested

B

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Flashbank