# SBOR (remote · mcp.sbor.xyz)

Check a lending rate before your agent borrows. Stacks benchmark, read from contract state. No key.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.sbor.xyz`: 58/100 (this document), [markdown](https://verifymcp.io/servers/xyz-sbor-sbor/mcp.md), [page](https://verifymcp.io/servers/xyz-sbor-sbor/mcp)
- npm · `sbor-mcp`: 71/100, [markdown](https://verifymcp.io/servers/xyz-sbor-sbor/sbor-mcp.md), [page](https://verifymcp.io/servers/xyz-sbor-sbor/sbor-mcp)

## Channel facts

- Endpoint: `https://mcp.sbor.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 718 tokens (~119/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the SBOR MCP server?

SBOR is a hosted endpoint at https://mcp.sbor.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xyz-sbor-sbor 'https://mcp.sbor.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-sbor-sbor": {
      "url": "https://mcp.sbor.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-sbor-sbor": {
      "type": "http",
      "url": "https://mcp.sbor.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-sbor-sbor]
url = "https://mcp.sbor.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-sbor-sbor": {
      "type": "remote",
      "url": "https://mcp.sbor.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-sbor-sbor --url 'https://mcp.sbor.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-sbor-sbor:
    url: "https://mcp.sbor.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-sbor-sbor": {
      "Transport": "http",
      "Url": "https://mcp.sbor.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-sbor-sbor -t streamable-http -u 'https://mcp.sbor.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-sbor-sbor": {
      "type": "http",
      "url": "https://mcp.sbor.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 58)

First indexed and scored.

## MCP tools (6)

### `get_rate` (~111 tokens)

Get the current SBOR fixing

The benchmark borrow and supply rate for lending on Stacks, read from lending contract state. 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.

Input parameters:

- `index` (string): Currency index, or BTC-COLLATERAL-USDC for borrowing USDC against bitcoin on Base and Ethereum. Omit for all of them.

### `compare_rate` (~227 tokens)

Compare a rate against the SBOR benchmark

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 USDC loan against bitcoin (cbBTC or WBTC) on Base or Ethereum, compare with BTC-COLLATERAL-USDC; for lending on Stacks, 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.

Input parameters:

- `index` (string, required): Which benchmark: a Stacks currency index, or BTC-COLLATERAL-USDC for borrowing USDC against bitcoin on Base and Ethereum.
- `rate` (number, required): The rate offered, as a percentage between 0 and 100. 4.2 means 4.2%, not 0.042.
- `side` (string, required): Whether you would be borrowing or supplying.

### `list_markets` (~68 tokens)

List the lending markets behind a rate

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.

Input parameters:

- `index` (string): Currency index, or BTC-COLLATERAL-USDC. Omit for the Stacks indices.

### `get_history` (~82 tokens)

Get the SBOR history

Daily fixings since the index 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.

Input parameters:

- `days` (integer): How many days back, up to 200. Default 30.
- `index` (string, required): Which currency.

### `compare_chains` (~125 tokens)

Compare Stacks rates against the same markets on other chains

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 USDC against bitcoin on Base and Ethereum. Context only: none of these is ever a constituent of an SBOR index. Aave on Ethereum and Base and the bitcoin-collateral markets are read from contract state; the other venues come from DefiLlama, so small differences are expected for those.

Input parameters:

- `index` (string): Only markets comparable to this index. Omit for all.

### `get_methodology` (~49 tokens)

How SBOR is calculated

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-sbor-sbor/mcp#diagnostics

## Score history

- 2026-09-25: 58

## Common questions

### What is the SBOR MCP server?

SBOR is an MCP server listed in the public MCP registry as xyz.sbor/sbor. Check a lending rate before your agent borrows. Stacks benchmark, read from contract state. No key. This page covers its hosted endpoint (https://mcp.sbor.xyz/mcp).

### Is the SBOR MCP server safe to use?

SBOR scores 58 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SBOR MCP server expose?

SBOR exposes 6 tools: get_rate, compare_rate, list_markets, get_history, compare_chains, get_methodology. Their descriptions and schemas cost roughly 662 tokens of context every time the server is loaded.

### Does the SBOR MCP server require authentication?

No. We connected to SBOR without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SBOR MCP server still maintained?

SBOR is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.sbor.xyz/mcp
- Repository: https://github.com/sborxyz/sbor
- Website: https://sbor.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-sbor-sbor/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-sbor-sbor/mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-sbor-sbor/mcp