Home / MCP registry index / markets.borro/borro

Borro

markets.borro/borro in the official MCP registry. Endpoint https://borro.markets/mcp.

The registry describes it as: Stock lending on Robinhood Chain: read markets and prepare lends, loans, shorts and credit lines.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http borro https://borro.markets/mcp

{
  "mcpServers": {
    "borro": {
      "url": "https://borro.markets/mcp"
    }
  }
}

code --add-mcp '{"name":"borro","type":"http","url":"https://borro.markets/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

markets market health position trades prices bear_coins rules open_short close_short supply withdraw borrow repay bind_builder open_pair close_pair buy_with_eth open_long close_long farms farm_deposit farm_withdraw weekend buy_cover deposit_cover withdraw_cover settle_cover claim_cover options write_option buy_option post_bid cancel_order settle_series claim_option release_collateral credit_markets credit_line holder_benefits credit_open credit_pay credit_gas credit_bill credit_bill_header credit_repay credit_guardrails hold_open hold_pay hold_header hold_status hold_collect hold_end account_open account_trade trigger_set trigger_list trigger_cancel trigger_fire account_status and 15 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 2816c22937496a10. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/markets-borro-borro/badge.svg)](https://lazaretto.dev/mcp-registry/markets-borro-borro)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Finance and markets MCP servers