SBOR
REMOTE · MCP.SBOR.XYZ · 2 COMPONENTS · SCANNED SEP 25
Check a lending rate before your agent borrows. Stacks benchmark, read from contract state. No key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
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.
remote · mcp.sbor.xyz
claude mcp add --transport http xyz-sbor-sbor 'https://mcp.sbor.xyz/mcp'
{
"mcpServers": {
"xyz-sbor-sbor": {
"url": "https://mcp.sbor.xyz/mcp"
}
}
} {
"servers": {
"xyz-sbor-sbor": {
"type": "http",
"url": "https://mcp.sbor.xyz/mcp"
}
}
} [mcp_servers.xyz-sbor-sbor] url = "https://mcp.sbor.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-sbor-sbor": {
"type": "remote",
"url": "https://mcp.sbor.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-sbor-sbor --url 'https://mcp.sbor.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-sbor-sbor:
url: "https://mcp.sbor.xyz/mcp" {
"McpServers": {
"xyz-sbor-sbor": {
"Transport": "http",
"Url": "https://mcp.sbor.xyz/mcp"
}
}
} assistant mcp add xyz-sbor-sbor -t streamable-http -u 'https://mcp.sbor.xyz/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.sbor.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sbor.xyz | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7403c7e56393d938134ce51785b81c79 |
| SANs: sbor.xyz, mcp.sbor.xyz, *.mcp.sbor.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.sbor.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| sbor.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sbor.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sbor.xyz/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_chains Compare Stacks rates against the same markets on other chains ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | Only markets comparable to this index. Omit for all. |
No output schema declared.
No examples provided.
compare_rate Compare a rate against the SBOR benchmark ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | yes | Which benchmark: a Stacks currency index, or BTC-COLLATERAL-USDC for borrowing USDC against bitcoin on Base and Ethereum. |
| rate | number | yes | The rate offered, as a percentage between 0 and 100. 4.2 means 4.2%, not 0.042. |
| side | string | yes | Whether you would be borrowing or supplying. |
No output schema declared.
No examples provided.
get_history Get the SBOR history ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days back, up to 200. Default 30. |
| index | string | yes | Which currency. |
No output schema declared.
No examples provided.
get_methodology How SBOR is calculated ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rate Get the current SBOR fixing ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | Currency index, or BTC-COLLATERAL-USDC for borrowing USDC against bitcoin on Base and Ethereum. Omit for all of them. |
No output schema declared.
No examples provided.
list_markets List the lending markets behind a rate ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | Currency index, or BTC-COLLATERAL-USDC. Omit for the Stacks indices. |
No output schema declared.
No examples provided.
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.