# Shibui Finance (remote · mcp.shibui.finance)

9,900+ US equities, 64 years of prices, financials, technicals, and earnings. Ask in plain English.

- Trust score: 65/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.shibui.finance`: 65/100 (this document), [markdown](https://verifymcp.io/servers/finance-shibui-data/mcp.md), [page](https://verifymcp.io/servers/finance-shibui-data/mcp)

## Channel facts

- Endpoint: `https://mcp.shibui.finance/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (export_to_excel).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 53/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1526 tokens (~127/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http finance-shibui-data https://mcp.shibui.finance/mcp
```

### Codex

```toml
[mcp_servers.finance-shibui-data]
url = "https://mcp.shibui.finance/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "finance-shibui-data": {
      "type": "remote",
      "url": "https://mcp.shibui.finance/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add finance-shibui-data --url https://mcp.shibui.finance/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  finance-shibui-data:
    url: "https://mcp.shibui.finance/mcp"
```

### Other

```json
{
  "mcpServers": {
    "finance-shibui-data": {
      "type": "http",
      "url": "https://mcp.shibui.finance/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61, +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.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (12)

### `stock_data_query` (~216 tokens)

Query Stock Data

Stock prices, earnings, revenue, P/E, dividends, filings, screener, comparisons

Run a SQL query against 64 years of US stock market data.

REQUIRES calling get_database_schema then get_query_patterns first (in that order).

This tool has no schema or query patterns built in. Call get_database_schema
once, then get_query_patterns once, then use this tool. Queries will timeout
or return wrong results without the patterns from get_query_patterns.

Input parameters:

- `query` (string, required): Read-only SQL query to execute. Requires shibui. table prefix and a LIMIT clause.
- `user_prompt` (string, required): The user's most recent question or request that motivated this query, verbatim. If the latest turn is a short follow-up that only makes sense with earlier conversation context (e.g., 'now show me MSF…

Output parameters:

- `result` (array)

### `get_database_schema` (~171 tokens)

Load Database Schema

REQUIRED for US stock/financial queries, authoritative source, call FIRST

Use this tool when the user asks about stock prices, revenue, earnings,
earnings surprises (EPS estimates vs actuals), margins, P/E ratios,
valuations, dividends, balance sheets, cash flow, technical indicators
(RSI, MACD, SMA), stock screening, company comparisons, sector
analysis, SEC filings, insider trading filings,
or any analysis of US-exchange-listed companies.

Covers 9,500+ NYSE and NASDAQ companies with 64 years of daily prices,
quarterly financials, 56 technical indicators, and SEC EDGAR filing metadata.

Must be called once per session before using stock_data_query or any workflow tool.
After this tool returns, call get_query_patterns before writing any SQL.

Output parameters:

- `result` (string)

### `get_query_patterns` (~90 tokens)

Load Query Patterns

REQUIRED before stock_data_query, 23 SQL patterns prevent timeouts/wrong results

Must be called once per session immediately after get_database_schema. Contains
query patterns for time-series selection, return calculations, screening
joins, window functions, backtesting, and performance optimization.
Time-series queries will timeout or return wrong results without these patterns.
After this tool returns, call stock_data_query to execute SQL.

Output parameters:

- `result` (string)

### `load_fundamental_workflow` (~95 tokens)

Fundamental Analysis Workflow

Load fundamental workflow for valuation, cash flow, margins, balance sheet. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about company valuation, "is X a good buy", financial health, debt levels, profitability ratios, revenue trends, earnings quality, or any deep-dive company analysis. Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_technical_workflow` (~115 tokens)

Technical Analysis Workflow

Load technical workflow for RSI, MACD, SMA, Bollinger Bands, entry/exit. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about RSI, MACD, moving averages, Bollinger Bands, support/resistance, overbought/oversold, momentum, trend, chart patterns, golden cross, entry/exit signals, or "is X oversold/overbought". Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_screening_workflow` (~106 tokens)

Stock Screening Workflow

Load screening workflow to find, filter, scan, rank stocks, top N by.... REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks to find, screen, scan, rank, or filter stocks — "find stocks that...", "top 10 by...", "best dividend stocks", value/growth screens, sector ranking, or any multi-factor selection. Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_comparison_workflow` (~92 tokens)

Peer Comparison Workflow

Load comparison workflow for X vs Y, peer analysis, relative valuation. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks to compare companies, "X vs Y", "how does X compare to Y", peer benchmarking, sector peers, side-by-side metrics, or relative valuation. Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_earnings_workflow` (~96 tokens)

Earnings Analysis Workflow

Load earnings workflow for EPS surprises, beat/miss, estimates, revenue. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, "did X beat estimates", quarterly earnings, revenue growth trends, earnings season, or estimates vs actuals. Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_backtesting_workflow` (~153 tokens)

Backtesting Analysis Workflow

Backtesting and simulation guardrails: survivorship, drawdown, Sharpe, day-of-week. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks to backtest, simulate, validate a strategy, test "what happens after X", compare forward returns, measure win rates or hit rates, compute Sharpe, drawdown, profit factor, rotation strategies, basket returns, or any hypothetical return over past data. Contains hard rules for survivorship bias, outlier handling, sampling design, day-of-week filters, and risk-adjusted metrics (Sharpe, Sortino, drawdown). Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_filing_workflow` (~152 tokens)

SEC Filing Analysis Workflow

Load filing workflow for SEC/EDGAR metadata, 8-K events, 10-K/10-Q reports. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL whenever the user asks about filing dates, filing activity, "who filed", "filed a form", filing frequency, SEC filings, EDGAR, 8-K events, 10-K/10-Q reports, proxy statements, or any query involving the sec_filings table (metadata - when/what type, not transaction detail). For insider transaction detail (shares, prices, cluster buying), use load_insider_workflow instead. Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `load_insider_workflow` (~137 tokens)

Insider Transaction Workflow

Load insider workflow for Form 3/4/5, insider buy/sell, cluster buy, 13D/G. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about insider transactions, insider buying/selling, Form 3 initial holdings, Form 4/5 transactions, cluster buying, executive purchases, officer sales, 10b5-1 plans, activist stakes, 13D/G filings, beneficial ownership, "who is buying/selling", or "track this insider across companies". Can be combined with other workflow tools.

Output parameters:

- `result` (string)

### `export_to_excel` (~103 tokens)

Export to Excel

Export query results to a branded Shibui Finance Excel spreadsheet.

Runs the same SQL query as stock_data_query but returns a downloadable
Excel file instead of raw data. The spreadsheet includes branded headers,
smart number formatting, and auto-fitted columns.

Input parameters:

- `query` (string, required): The SQL query to execute and export. Same query used with stock_data_query.
- `title` (string, required): Title for the spreadsheet header (e.g. "Mega-Cap Stock Comparison").

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/finance-shibui-data/mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://mcp.shibui.finance/mcp
- Changelog RSS feed: https://verifymcp.io/servers/finance-shibui-data/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/finance-shibui-data/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/finance-shibui-data/mcp