SBOR vs Visibility Index
A side-by-side look at the SBOR and Visibility Index MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SBOR for finance & fintech work as a local process; choose Visibility Index for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SBOR when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_rate, compare_rate, list_markets.
Choose Visibility Index when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_visibility_index, get_brand_visibility, list_tracked_brands.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 61/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 5 |
| Full listing | View SBOR | View Visibility Index |
Tools & capabilities
SBOR tools 6
get_rateSBOR'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.compare_rateGiven 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.list_marketsEvery 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.get_historyDaily 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.compare_chainsThe 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.get_methodologyThe 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.
Visibility Index tools 5
get_visibility_indexThe whole current release in one call: every tracked brand in SaaS & AI tools with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 20 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers SaaS & AI tools only; the sibling index at dablock.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.get_brand_visibilityOne brand's standing in the current DABYTE release: share of answer per engine, rank, quadrant, how many panel prompts name it, and which ones. Use this when a specific brand is named. Takes a slug, not a display name — call list_tracked_brands first if you are unsure, or read the slug from get_visibility_index. An unknown slug is not a failure to hide: the error names every valid slug, so a second attempt can succeed. A brand absent from the index has not been measured at all, which is different from a measured zero. Only SaaS & AI tools brands are tracked. For the field as a whole use get_visibility_index; for this brand over time, get_history. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.list_tracked_brandsThe names and slugs of every brand in the DABYTE index — a lookup table, nothing else. No scores, no ranks. Use it for two things: to turn a brand name into the slug get_brand_visibility needs, and to answer whether a brand is tracked at all. Do NOT use it when you want figures — get_visibility_index returns the same brands with their full measurements in a single call, so calling this one first is a wasted round trip. Absence here means the brand is not measured, not that it scores zero. Covers SaaS & AI tools only; the sibling index at dablock.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.get_historyEvery DABYTE release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.get_methodologyThe rules behind every figure this server returns: the exact prompt panel and its version, which engines were measured, how share of answer is scored and rounded, the resolution of the scale in percentage points, and the editorial firewall and ownership disclosure. Call this before quoting a number as evidence, before comparing two releases, or whenever a user asks how the measurement was made or who publishes it. It is the only tool that tells you how much of a difference is meaningful, which is what stops a one-step wobble being reported as a movement. It returns rules, not figures — no brand appears in the response. For figures use get_visibility_index or get_brand_visibility; for the series, get_history. The panel is public and frozen between releases, so every published number can be recomputed by a third party from the archive at https://dabyte.ai/archive/. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SBOR
{
"mcpServers": {
"sbor": {
"command": "npx",
"args": [
"-y",
"sbor-mcp"
]
}
}
}
Visibility Index
{
"mcpServers": {
"visibility-index": {
"url": "https://dabyte.ai/mcp"
}
}
}
Frequently asked questions
SBOR is categorized under Finance & Fintech and uses a local stdio subprocess. Visibility Index belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick SBOR for finance & fintech work and Visibility Index for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SBOR has no declared pricing — check the project's own site. Visibility Index has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sbor and visibility-index as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SBOR has a quality signal of 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Visibility Index has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.