Bamsai
REMOTE · BAMSAI.KR
Korean blue chips priced 24/7 from Hyperliquid perps in KRW: pre-open price and arbitrage
Available components
Last scanned (19 hours ago)
Scores higher than 57% 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
- Authorisation not fully verified: no authorisation is required to call this server, and 5 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 902 tokens (~180/item across 5 items; 5 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 (12)
- TLS certificate
- HTTPS
- 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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
- Tool “get_arbitrage” rewrote its description, which is the text the model reads security
- Tool “get_news” rewrote its description, which is the text the model reads security
- Tool “predict_open” rewrote its description, which is the text the model reads security
- Schema quality: 155 → 180 ▼ functional
- Tool coverage: 80% → 100% ▲ functional
- “get_convergence_history” reworded the description of “limit” cosmetic
- “preview_pair_order” reworded the description of “direction” cosmetic
- 7 Nov 26 +1
- Tool “get_arbitrage” rewrote its description, which is the text the model reads security
- Schema quality: 121 → 155 ▼ functional
- Tool coverage: 63% → 80% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “get_arbitrage” added an optional parameter “lagSec” cosmetic
- “get_arbitrage” added an optional parameter “notionalKrw” cosmetic
- “preview_pair_order” reworded the description of “notionalKrw” cosmetic
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://bamsai.kr/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bamsai.kr | CN=YR1,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | RSA 2048 | SHA256-RSA | 64861455ec80ce30a9002c221f70caac4b8 |
| SANs: bamsai.kr | ||||||
| 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 bamsai.kr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| kr. | DS published | 64641 | 13 | Verified |
| bamsai.kr. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bamsai.kr/api/mcp | Verified | 200 | |
| http (plaintext) | http://bamsai.kr/api/mcp | HTTPS enforced | 308 | https://bamsai.kr/api/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 →
get_arbitrage ~259
Premium between Hyperliquid perp (mid) and KRX price, its usual level (5-day regular-session median) and the net left after costs on the gap beyond that level. net.netPct subtracts fees, tax, FX, funding, order-book slippage for notionalKrw (net.costs.slippage, net.fills: volume-weighted fill prices per leg) and the price move during the gap between the two orders (net.costs.latency = 1-minute volatility × √(lagSec/60)). net.depthLimited / net.maxNotionalKrw: the visible book can fill less than notionalKrw. oracle.active: oracle-anomaly window (thin print moved the oracle); numbers stay on the real book, oracle.warning flags liquidation risk. All assets if asset is omitted
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | SMSN=Samsung Electronics, SKHX=SK hynix, HYUNDAI=Hyundai Motor, SKHY=SK hynix ADR (vs 0.1 common share) |
| lagSec | number | – | Seconds between the two orders (default 3) |
| notionalKrw | number | – | Trade size per leg in KRW (default 10000000) |
No output schema declared.
No examples provided.
get_convergence_history ~118
Past re-open record per day since 2026-04-13: Hyperliquid move while closed (20:00→08:00), actual re-open move, follow (yes/no/flat), and where the prices met. Newest first, 20 days unless limit is given
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | SMSN=Samsung Electronics, SKHX=SK hynix, HYUNDAI=Hyundai Motor |
| limit | number | – | How many most recent re-opens to return (default 20) |
No output schema declared.
No examples provided.
get_news ~106
One sourced news item per day for an asset (the day's main issue, with title, summary and source link), to explain big overnight or opening moves
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | SMSN=Samsung Electronics, SKHX=SK hynix, HYUNDAI=Hyundai Motor, SKHY=SK hynix ADR (0.1 share), KR200=KOSPI 200, EWY=MSCI Korea ETF, KORU=3x Korea ETF |
No output schema declared.
No examples provided.
predict_open ~206
Where the next domestic re-open (08:00–08:10 average on KRX/NXT, vs the 20:00 close) stands, for SMSN/SKHX/HYUNDAI. While the domestic market trades, status=in-session and preOpen is Hyperliquid at today's 08:00 open. Otherwise: the Hyperliquid price in KRW now and at the US close, how often past re-opens followed Hyperliquid at this stage of the night (night.follow.ratePct), the 80% band, and the overall follow rate (backtest.followRatePct). probUp and the expected price are model output, not a promise. oracle.active: oracle-anomaly window; the Hyperliquid price then is oracle.robustKrw (30-minute median), not the spiking live mid
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | SMSN=Samsung Electronics, SKHX=SK hynix, HYUNDAI=Hyundai Motor |
No output schema declared.
No examples provided.
preview_pair_order ~213
Preview (dry-run) of an arbitrage pair order: stock quantity and the Hyperliquid order it would send. Nothing is ever sent from this server. Hyperliquid side is priced on testnet (the default network), so its price can differ from mainnet
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | SMSN=Samsung Electronics, SKHX=SK hynix, HYUNDAI=Hyundai Motor, SKHY=SK hynix ADR (0.1 share), KR200=KOSPI 200, EWY=MSCI Korea ETF, KORU=3x Korea ETF |
| direction | string | yes | perp_short_stock_long = sell the Hyperliquid perp and buy the stock (the only direction retail can do without short-selling stock). Use net.direction from get_arbitrage |
| notionalKrw | number | yes | Trade size in KRW. get_arbitrage with the same notionalKrw shows the expected fill prices, slippage and net for this size |
No output schema declared.
No examples provided.
How do I install the Bamsai MCP server?
Bamsai is a hosted endpoint at https://bamsai.kr/api/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 · bamsai.kr
claude mcp add --transport http eddyparkgg-bamsai 'https://bamsai.kr/api/mcp'
What is the Bamsai MCP server?
Bamsai is an MCP server listed in the public MCP registry as io.github.eddyParkGG/bamsai. Korean blue chips priced 24/7 from Hyperliquid perps in KRW: pre-open price and arbitrage. This page covers its hosted endpoint (https://bamsai.kr/api/mcp).
Is the Bamsai MCP server safe to use?
Bamsai scores 72 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 Bamsai MCP server expose?
Bamsai exposes 5 tools: get_arbitrage, predict_open, get_convergence_history, get_news, preview_pair_order. Their descriptions and schemas cost roughly 902 tokens of context every time the server is loaded.
Does the Bamsai MCP server require authentication?
No. We connected to Bamsai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bamsai MCP server still maintained?
Bamsai 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 Bamsai MCP server?
VerifyMCP ran 12 checks on Bamsai, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Bamsai: Authorization. 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.