SBOR
REMOTE · MCP.SBOR.XYZ · 2 COMPONENTS
Check a lending rate before your agent borrows. Bitcoin-backed dollar rates from contracts. No key.
Available components
Last scanned (12 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1001 tokens (~166/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 17 Nov 26 0
- Server version: 1.4.0 → 1.4.1 functional
- “compare_rate” reworded the description of “rate” cosmetic
- 13 Nov 26 −1
- Tool “get_rate” rewrote its description, which is the text the model reads security
- Server version: 1.3.0 → 1.4.0 functional
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 +1
- Stability: 0.97 → pass security
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 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. | DS published | 3599, 18130 | 8, 8 | Verified |
| sbor.xyz. | No DS | 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 ~148
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.
| 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 ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | yes | Which benchmark: BTC-COLLATERAL-USD or BTC-COLLATERAL-<stablecoin> for borrowing dollars against bitcoin, or a Stacks currency index. |
| rate | number | yes | The rate offered, as a percentage from 0 to 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 ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days back, up to 200. Default 30. |
| index | string | yes | A Stacks currency index, BTC-COLLATERAL-USD (from 14 October 2026), or BTC-COLLATERAL-<stablecoin>. |
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 ~200
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, with the compounded 30, 90 and 180-day averages once each window is full. Always read the freshness line first. A fixing withdrawn after publication is reported as withdrawn, never as a rate.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | 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. |
No output schema declared.
No examples provided.
list_markets List the lending markets behind a rate ~81
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 | – | BTC-COLLATERAL-USD, BTC-COLLATERAL-<stablecoin>, or a Stacks currency index. Omit for the Stacks indices. |
No output schema declared.
No examples provided.
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'
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. Bitcoin-backed dollar rates from contracts. No key. This page covers its hosted endpoint (https://mcp.sbor.xyz/mcp).
Is the SBOR MCP server safe to use?
SBOR scores 77 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 837 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the SBOR MCP server?
VerifyMCP ran 12 checks on SBOR, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SBOR: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.