Basis Protocol
REMOTE · BASISPROTOCOL.XYZ · SCANNED OCT 8
Attested risk scores for stablecoins, DeFi protocols and wallets, with receipts.
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 Security63
- 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 24 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2212 tokens (~92/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 25 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
How do I install the Basis Protocol MCP server?
Basis Protocol is a hosted endpoint at https://basisprotocol.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 · basisprotocol.xyz
claude mcp add --transport http basis-protocol-basis 'https://basisprotocol.xyz/mcp'
{
"mcpServers": {
"basis-protocol-basis": {
"url": "https://basisprotocol.xyz/mcp"
}
}
} {
"servers": {
"basis-protocol-basis": {
"type": "http",
"url": "https://basisprotocol.xyz/mcp"
}
}
} [mcp_servers.basis-protocol-basis] url = "https://basisprotocol.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"basis-protocol-basis": {
"type": "remote",
"url": "https://basisprotocol.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add basis-protocol-basis --url 'https://basisprotocol.xyz/mcp' --transport streamable-http
mcp_servers:
basis-protocol-basis:
url: "https://basisprotocol.xyz/mcp" {
"McpServers": {
"basis-protocol-basis": {
"Transport": "http",
"Url": "https://basisprotocol.xyz/mcp"
}
}
} assistant mcp add basis-protocol-basis -t streamable-http -u 'https://basisprotocol.xyz/mcp'
{
"mcpServers": {
"basis-protocol-basis": {
"type": "http",
"url": "https://basisprotocol.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.
- 8 Oct 26 +1
- Tool “basis_governance_activity” rewrote its description, which is the text the model reads security
- Tool “query_template” rewrote its description, which is the text the model reads security
- New tool “basis_asset_footprint” functional
- 6 Oct 26 +1
- Tool “get_stablecoin_scores” rewrote its description, which is the text the model reads security
- “get_stablecoin_scores” added an optional parameter “full” cosmetic
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- New tool “basis_venue_shift” functional
- 30 Sept 26 +38
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 22 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 28 Sept 26 25
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 8 Oct 2026 · Probed https://basisprotocol.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=basisprotocol.xyz | CN=YR1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 59f9a792aa110e71f428fd3e0821c9360da |
| SANs: basisprotocol.xyz | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of basisprotocol.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| basisprotocol.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://basisprotocol.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://basisprotocol.xyz/mcp | HTTPS enforced | 301 | https://basisprotocol.xyz/mcp |
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 →
basis_answer ~285
Ask the Basis Agent a question about attested risk state. Answers come ONLY from attested substrate state, cited to attestation hashes; queries the substrate cannot ground are refused (identical envelope, refusals, and receipts as the REST transport — the agent never recommends positions, never forecasts, never executes). Every call is logged as an attributed protocol read. Identity: pass your hub API key on the /mcp HTTP request (``x-api-key`` header or ``?apikey=`` query param) so reads are attributed to your service; keyless calls are attributed by IP. Multi-turn: the returned envelope carries ``session_id`` — pass it back as the ``session_id`` argument on your next call to hold a session (follow-ups like "and its liquidity?" then inherit the session's entity). An ``X-Basis-Session`` header on the /mcp request works too; the explicit argument wins. Omit both and each call is a fresh single-turn session. Parameters: query: The question (max 4000 chars). session_id: Session UUID from a previous basis_answer envelope (optional — enables multi-turn follow-ups).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_asset_footprint ~111
Where a collateral token is used across the lending venues we read: per venue and chain, supply and borrow against it and its share of the venue's supply. Supply/borrow are the markets' loan-side totals attributed to the collateral token (a footprint proxy, not collateral posted). Phantom / single-actor flagged markets are listed, not summed. A symbol matching several tokens returns them separately (ambiguous=true).
| Name | Type | Req | Description |
|---|---|---|---|
| token_or_symbol | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_bridge_flows ~79
Directional bridge volume per chain pair. Shows where capital is flowing: "$50M Ethereum → Arbitrum, $12M back." Use to assess cross-chain liquidity routing and chain health. Parameters: bridge_id: Specific bridge ID (optional). Omit for aggregate flows.
| Name | Type | Req | Description |
|---|---|---|---|
| bridge_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_correlation ~85
Cross-entity correlation matrix. Shows which assets move together. When USDC depegs, which protocols lose TVL in sync? Use for portfolio construction and systemic risk assessment. Parameters: matrix_type: "sii_30d", "sii_90d", or "cross_90d"
| Name | Type | Req | Description |
|---|---|---|---|
| matrix_type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_data_catalog ~59
Every data type available in the universal data layer. Returns per data type: description, freshness, history depth, update frequency, provenance status, row count. Use to discover what data is available for building custom risk indices.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_exchange_health ~88
Exchange trust score, volume, and reserve status. Returns CoinGecko trust scores, 24h volume, year established, and stablecoin-specific trading pair data for top exchanges. Parameters: exchange_id: CoinGecko exchange ID (e.g. "binance", "coinbase-exchange"). Omit for all.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_governance_activity ~133
Governance proposal counts, voter participation, and pass rates. Returns full proposal history with vote counts, quorum status, and voter concentration data. Use to assess DAO health and governance quality. Parameters: protocol: Protocol slug as used by the Basis protocol index (e.g. "aave", "lido", "curve-finance", "compound-finance", "uniswap"). Snapshot space names such as "aavedao" are not accepted. days: Lookback period in days (default 90)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| protocol | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_incidents ~79
Structured event history: exploits, depegs, oracle failures. Returns timeline of incidents with severity, affected entities, and resolution status. Use for due diligence and insurance risk assessment. Parameters: entity_id: Entity ID to filter by (optional). Omit for all recent incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_liquidity_depth ~119
Per-asset, per-venue liquidity profile for any stablecoin. Returns DEX pool depth (Uniswap, Curve, etc.) and CEX ticker data (Binance, Coinbase, etc.) with bid/ask depth, spread, volume, and trade counts. Use before any large stablecoin transaction to check venue liquidity. Parameters: asset_id: Stablecoin ID (e.g. "usdc", "usdt", "dai")
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_peg_monitor ~114
5-minute peg resolution data for micro-depeg detection. Returns 5-minute price snapshots and deviation from $1.00. Catches micro-depegs that are invisible at hourly resolution. Early warning signal for peg instability. Parameters: stablecoin_id: Stablecoin ID (e.g. "usdc", "usdt") hours: Lookback period in hours (default 24)
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| stablecoin_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_venue_shift ~83
Venue-shift findings: an operator's proposed venue markets overlapped against the markets its vaults currently allocate to. Each finding cites the proposal capture hash and the allocation-snapshot attestation it was computed from. Omit operator_slug to list all findings, sorted by share of venue supply.
| Name | Type | Req | Description |
|---|---|---|---|
| operator_slug | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_volatility ~91
Realized volatility, drawdown, and recovery time for any asset. Returns 1d/7d/30d/90d realized vol, max drawdown, and correlation with BTC/ETH. Use for risk-adjusted position sizing. Parameters: asset_id: Asset ID (e.g. "usdc", "usdt")
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
basis_yield_data ~102
Pool-level yield, TVL, and utilization for any DeFi protocol. Returns APY, base APY, reward APY, TVL, and pool metadata for all tracked lending/vault pools. Use to evaluate yield sustainability and protocol health. Parameters: protocol: Protocol slug (e.g. "aave-v3", "compound-v3"). Omit for all protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_transaction_risk ~51
Composite risk assessment for a stablecoin transaction — evaluates asset, sender, and receiver.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_symbol | string | yes | – |
| from_address | string | yes | – |
| to_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_divergence_signals ~101
Check for divergence signals before executing transactions. Detects capital-flow / quality mismatches: - Asset quality: stablecoin score declining while capital flows in - Wallet concentration: HHI rising while wallet value grows - Quality-flow: score declining with net inflows from wallet graph Call this BEFORE executing any stablecoin swap, deposit, or rebalance to check if capital is flowing toward deteriorating assets.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_methodology ~26
Returns the current SII formula, category weights, score scale, and version information.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_riskiest_wallets ~36
Wallets with the most capital at risk — lowest risk scores weighted by total value.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_scoring_backlog ~34
Unscored stablecoin assets ranked by total capital exposure across all indexed wallets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_stablecoin_detail ~33
Full score breakdown for a specific stablecoin including category scores and methodology version.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_stablecoin_scores ~118
Get current SII scores (0-100) for all scored stablecoins. Use before any decision involving stablecoins. Returns a compact summary per coin (score, grade, confidence, category scores). Call get_stablecoin_detail for one coin's full breakdown. Parameters: sort_by: "score_desc" (default), "score_asc", or "symbol" full: true returns every field per coin (large)
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| sort_by | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_treasury_events ~130
Get recent behavioral events from labeled treasury wallets. Detects: TWAP conversions, protocol rebalancing, concentration drift, quality shifts, and large transfers (>$1M) from known treasury wallets. Parameters: wallet_address: Filter to a specific wallet (optional) event_type: Filter by type: twap_conversion, rebalance, concentration_drift, quality_shift, large_transfer days: Lookback period in days (default 30)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| event_type | string | – | – |
| wallet_address | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_wallet_holdings ~32
Detailed holdings breakdown for an Ethereum wallet with per-asset SII scores.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_wallet_risk ~35
Get risk profile for a specific Ethereum wallet — composite risk score, concentration, coverage quality.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query_template ~176
Run a pre-built query template against the Basis risk database. Available templates: - high_risk_whales: Wallets with high value AND poor risk scores - contagion_hotspots: Wallets with the most counterparty connections - stablecoin_concentration: Per-stablecoin holder concentration - score_movers: Assets whose SII score changed most over N days - disclosure_gaps: Issuers with the oldest attestation documents - cross_chain_exposure: Wallets active on multiple chains Call GET /api/query/templates first to list the exact template names and their parameters; an unknown name returns the list of valid names (do not invent names such as "basis protocol").
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | – |
| template_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Basis Protocol MCP server?
Basis Protocol is an MCP server listed in the public MCP registry as io.github.basis-protocol/basis. Attested risk scores for stablecoins, DeFi protocols and wallets, with receipts. This page covers its hosted endpoint (https://basisprotocol.xyz/mcp).
Is the Basis Protocol MCP server safe to use?
Basis Protocol scores 67 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 Basis Protocol MCP server expose?
Basis Protocol exposes 24 tools: get_stablecoin_scores, get_stablecoin_detail, get_wallet_risk, get_wallet_holdings, get_riskiest_wallets, and 19 more. Their descriptions and schemas cost roughly 2,200 tokens of context every time the server is loaded.
Does the Basis Protocol MCP server require authentication?
No. We connected to Basis Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Basis Protocol MCP server still maintained?
Basis Protocol is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.