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

sbor

https://mcp.sbor.xyz

Registry code: cc75638ee0d9b83d

api record

SBOR publishes benchmark lending rates for borrowing against bitcoin, read from contract state and published daily. From 14 October 2026 its headline is BTC-COLLATERAL-USD, what it costs to borrow any dollar stablecoin against plain bitcoin, with a rate per stablecoin (BTC-COLLATERAL-USDC, -USDT, -RLUSD, -PYUSD, -USD1); before that date, BTC-COLLATERAL-USDC. It also publishes an index per currency on Stacks. Each day's rates are also posted on-chain on Arc, Base, Hyperliquid, Solana and Stacks. Before borrowing, call compare_rate: if an offer is well above the benchmark, stop. Every tool…

endpoint
https://mcp.sbor.xyz/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 sbor live?
Yes — it answered the hub's last check (checked 5m ago). It answered 100% of checks over the last 30 days.
Is sbor free to use?
Yes — the hub reached it with no key and no payment.
What tools does sbor have?
6 tools: compare_rate, get_history, get_methodology, get_rate, list_markets, compare_chains.
Is sbor 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
99.6%

90 days 99.8%· all time 99.8%

latency
433ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 434 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get bitcoin defi lending benchmark rate
  • compare offered borrow rate
  • get lending rate history
  • compare lending markets across chains
takes → gives
text → data
tools
6 reads
_ 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
4 open 2 never probed 4 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.

  • get_methodology reads open 18h ago

    The full methodology and integration policy: how the fixing is built, what is excluded and why, and what SBOR will and will not do. Read this before quoting a rate in anything that matters.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_rate reads open 8h ago

    SBOR's benchmark borrow and supply rates, read from lending contract state: BTC-COLLATERAL-USD, what it costs to borrow dollars against bitcoin, with a rate per stablecoin (from 14 October 2026), and the currency indices for lending on Stacks. Use this to judge whether a lending offer is good: borrowing above the SBOR borrow rate means paying more than the market, supplying below the supply rate means earning less. Returns every currency index unless one is named. Always read the freshness line first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "index": {
          "enum": [
            "SBOR-USD",
            "SBOR-BTC",
            "SBOR-STX",
            "BTC-COLLATERAL-USD",
            "BTC-COLLATERAL-USDC",
            "BTC-COLLATERAL-USDT",
            "BTC-COLLATERAL-RLUSD",
            "BTC-COLLATERAL-PYUSD",
            "BTC-COLLATERAL-USD1"
          ],
          "type": "string",
          "description": "BTC-COLLATERAL-USD for borrowing any dollar stablecoin against bitcoin, BTC-COLLATERAL-<stablecoin> for one stablecoin, or a Stacks currency index. Omit for all of them."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • list_markets reads open 8h ago

    Every venue and asset in an index, with its borrow rate, supply rate, utilization, depth and weight. Utilization explains why a rate sits where it does.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "index": {
          "enum": [
            "SBOR-USD",
            "SBOR-BTC",
            "SBOR-STX",
            "BTC-COLLATERAL-USD",
            "BTC-COLLATERAL-USDC",
            "BTC-COLLATERAL-USDT",
            "BTC-COLLATERAL-RLUSD",
            "BTC-COLLATERAL-PYUSD",
            "BTC-COLLATERAL-USD1"
          ],
          "type": "string",
          "description": "BTC-COLLATERAL-USD, BTC-COLLATERAL-<stablecoin>, or a Stacks currency index. Omit for the Stacks indices."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • compare_chains reads open 8h ago

    The same asset classes on the largest lending markets on Ethereum, Base, Hyperliquid and Solana, plus SOFR, the US repo rate, and what it costs to borrow dollars against bitcoin. Context only: none of these is ever a constituent of an SBOR index. Every rate is read from the venues' contracts (Aave on Ethereum and Base, HyperLend on Hyperliquid, Kamino on Solana, Morpho for the bitcoin-collateral markets); DefiLlama picks the largest market per chain, gives its size, and stands in only if a read fails.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "index": {
          "enum": [
            "SBOR-USD",
            "SBOR-BTC",
            "SBOR-STX"
          ],
          "type": "string",
          "description": "Only markets comparable to this index. Omit for all."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • compare_rate reads unknown 18h ago

    Given a rate you have been offered, say whether it is above or below the market for that currency, and by how much. This is the main reason SBOR exists. Recommended use: if a borrow offer is more than 50 basis points above the benchmark, stop and ask a human. Use SBOR to stop, never to start. For a dollar loan against bitcoin, compare with that stablecoin's rate (for example BTC-COLLATERAL-USDC) where one is published, else with BTC-COLLATERAL-USD; for lending on Stacks against other collateral, with the index for the currency. This tool refuses rather than guesses: an error result means there is no trustworthy answer, not that the rate is bad.

    mcp-tool

    {
      "type": "object",
      "required": [
        "rate",
        "side",
        "index"
      ],
      "properties": {
        "rate": {
          "type": "number",
          "maximum": 100,
          "description": "The rate offered, as a percentage between 0 and 100. 4.2 means 4.2%, not 0.042.",
          "exclusiveMinimum": 0
        },
        "side": {
          "enum": [
            "borrow",
            "supply"
          ],
          "type": "string",
          "description": "Whether you would be borrowing or supplying."
        },
        "index": {
          "enum": [
            "SBOR-USD",
            "SBOR-BTC",
            "SBOR-STX",
            "BTC-COLLATERAL-USD",
            "BTC-COLLATERAL-USDC",
            "BTC-COLLATERAL-USDT",
            "BTC-COLLATERAL-RLUSD",
            "BTC-COLLATERAL-PYUSD",
            "BTC-COLLATERAL-USD1"
          ],
          "type": "string",
          "description": "Which benchmark: BTC-COLLATERAL-USD or BTC-COLLATERAL-<stablecoin> for borrowing dollars against bitcoin, or a Stacks currency index."
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • get_history reads unknown 18h ago

    Daily fixings since each rate began. Use this to see whether a rate is unusual, or how the cost of capital has moved. Means are given per methodology version, never across a change in how the number is built.

    mcp-tool

    {
      "type": "object",
      "required": [
        "index"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "How many days back, up to 200. Default 30."
        },
        "index": {
          "enum": [
            "SBOR-USD",
            "SBOR-BTC",
            "SBOR-STX",
            "BTC-COLLATERAL-USD",
            "BTC-COLLATERAL-USDC",
            "BTC-COLLATERAL-USDT",
            "BTC-COLLATERAL-RLUSD",
            "BTC-COLLATERAL-PYUSD",
            "BTC-COLLATERAL-USD1"
          ],
          "type": "string",
          "description": "A Stacks currency index, BTC-COLLATERAL-USD (from 14 October 2026), or BTC-COLLATERAL-<stablecoin>."
        }
      },
      "additionalProperties": false
    }
    arguments 30 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 cc75638ee0d9b83d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cc75638ee0d9b83d/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/cc75638ee0d9b83d/badge.svg)](https://brick.blue/agent/cc75638ee0d9b83d?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.