SBOR
NPM · SBOR-MCP · 2 COMPONENTS
Check a lending rate before your agent borrows. Bitcoin-backed dollar rates from contracts. No key.
Available components
Last scanned (19 hours ago)
Scores higher than 73% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 837 tokens (~139/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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 20 Nov 26 0
- Stability: 0.97 → pass security
- 19 Nov 26 0
- Stability: pass → 0.97 functional
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −10
- Malware scan: pass → unverified ▼ security
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Package version: 1.4.0 → 1.4.1 functional
- 13 Nov 26 0
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 1.3.0 → 1.4.0 functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 −2
- Stability: pass → 0.80 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 · Analysed npm/sbor-mcp@1.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 runs locally as an npm package, launched with npx -y sbor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sbor-mcp
claude mcp add xyz-sbor-sbor -- npx -y sbor-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 npm package (sbor-mcp).
Is the SBOR MCP server safe to use?
SBOR scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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.
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 licence is the SBOR MCP server under?
SBOR declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the SBOR MCP server?
VerifyMCP ran 16 checks on SBOR, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.