CantorFi MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
CantorFi is a lending protocol on Base made of isolated vaults: each vault lends one token against collateral in that same token, with borrow and supply rates derived from utilization. It also settles prediction markets and inspects B20 tokens. The public deployment runs on Base Sepolia (chain 84532). Use cantorfi_vaults for the live state of every vault, cantorfi_vault for one vault, cantorfi_contracts for the deployed addresses, cantorfi_liquidation_bot for the open-source liquidation bot, and search then fetch for the guides. This server is read-only and never holds keys: supplying, borrowing and liquidating are signed by the user's own wallet in the application or the bot.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cantorfi_vaultsA | Live state of every CantorFi isolated lending vault: token, supplied, borrowed, available liquidity, utilization, borrow and supply APR, borrow limit, liquidation threshold and liquidation bonus. |
| cantorfi_vaultA | Live state of one CantorFi vault, chosen by token symbol (USDC, WETH), vault id or vault address. |
| cantorfi_contractsA | Network, chain id, deployment block and addresses of the CantorFi contracts: protocol registry, vault factory, reader, price oracle and every vault with its token, receipt token and staking contract. |
| cantorfi_liquidation_botA | How to run the open-source CantorFi liquidation bot: read-only without a key, or liquidating with the user's own wallet. Returns the repository and the commands filled with the network values. |
| searchA | Search CantorFi vaults and guides (isolated lending, liquidations, prediction market settlement, B20 tokens, ERC-4626); returns ids for fetch. |
| fetchA | Full record of one CantorFi vault or full text of one guide, by id (from search). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The vault-list vs single-vault split is clear (cantorfi_vaults vs cantorfi_vault), and contracts/liquidation-bot tools are distinct. The generic search/fetch tools overlap somewhat with the vault-state tools in the vault domain, but their id-based retrieval workflow is described well enough to distinguish them.
Four tools follow a cantorfi_<resource> snake_case pattern, but search and fetch are bare generic verbs with no CantorFi prefix or resource noun. The set is readable but mixes domain-prefixed noun names with generic action names rather than following one predictable convention.
Six tools is well within the appropriate range for a focused protocol-information MCP server. Each tool maps to a distinct capability: vault list, vault detail, contract metadata, liquidation-bot guidance, search, and fetch.
The surface covers vault state, contract addresses, liquidation-bot guidance, and searchable docs, which is solid for a read-only information server. However, it lacks obvious lending-domain operations such as user position/health-factor lookup, liquidation candidate discovery, oracle price retrieval, or transaction preparation.