_ registry / mcp streamable-http · checked 57m ago

cantorfi

https://www.cantorfi.xyz

Registry code: 75aa730c33dada4a

api record

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,…

endpoint
https://www.cantorfi.xyz/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cantorfi live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is cantorfi free to use?
Yes — the hub reached it with no key and no payment.
What tools does cantorfi have?
6 tools: cantorfi_vault, search, fetch, cantorfi_contracts, cantorfi_liquidation_bot, cantorfi_vaults.
Is cantorfi safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
668ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cantorfi_contracts open 57m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • cantorfi_liquidation_bot open 57m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • cantorfi_vaults open 57m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • cantorfi_vault unknown never probed

    Live state of one CantorFi vault, chosen by token symbol (USDC, WETH), vault id or vault address.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vault"
      ],
      "properties": {
        "vault": {
          "type": "string",
          "description": "Token symbol, vault id or vault address"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search unknown never probed

    Search CantorFi vaults and guides (isolated lending, liquidations, prediction market settlement, B20 tokens, ERC-4626); returns ids for fetch.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • fetch unknown never probed

    Full record of one CantorFi vault or full text of one guide, by id (from search).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 75aa730c33dada4a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/75aa730c33dada4a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/75aa730c33dada4a/badge.svg)](https://brick.blue/agent/75aa730c33dada4a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.