Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SBChart2.0 MCP

REMOTE · SOFTBOWL.CO.KR

Softbowl SBChart2.0 차트(chart) 라이브러리의 공식 API 문서를 검색해, AI가 정확한 차트 코드를 생성하도록 돕습니다.

Available components

0 this week 71 Trust /100

Last scanned (18 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2980 tokens (~745/item across 4 items; 4 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 4 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
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

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 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Aug 26 0
    • Stability: 0.97 → pass security
Diagnostics

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://softbowl.co.kr/mcp/sbchart2.do

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=softbowl.co.kr CN=YR1,O=Let's Encrypt,C=US 18 Nov 2026 16 Feb 2027 RSA 2048 SHA256-RSA 635cc33605480cc192a09e0069d58f16012
SANs: softbowl.co.kr, www.softbowl.co.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 softbowl.co.kr. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
kr. DS published 64641 13 Verified
co.kr. DS published 8875 13 Verified
softbowl.co.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://softbowl.co.kr/mcp/sbchart2.do Verified 200
http (plaintext) http://softbowl.co.kr/mcp/sbchart2.do Inconclusive 405
MCP tools · 4 exposed · ~641 tokens

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 →

Tool Tokens
getSBChartAPIDetail ~166

Get the full documentation for one SBChart2.0 option/API by exact name: detailed explanation, HTML/JS usage, example, and warnings. Use after searchSBChartAPI. For a chart type's data structure, query its 'dataFormat' entry (e.g. 'Gantt 차트 데이터 포맷'). ⚠️ SBChart2.0 코드/샘플 생성 시 서버 공통지침(표준 골격에서 출발 · chartConfig 리터럴 나열 · 요청 기능만 최소 적용) 준수 — 상세는 서버 instructions 참고.

NameTypeReqDescription
namestringyesExact option/API name as shown in searchSBChartAPI results (e.g. 'barFormat', 'Gantt 차트 데이터 포맷').

No output schema declared.

No examples provided.

getSBChartExample ~156

Find runnable SBChart2.0 code examples by feature or use case. Returns example code (data + config) for a chart type or option. Use when you want working sample code rather than the API reference. ⚠️ SBChart2.0 코드/샘플 생성 시 서버 공통지침(표준 골격에서 출발 · chartConfig 리터럴 나열 · 요청 기능만 최소 적용) 준수 — 상세는 서버 instructions 참고.

NameTypeReqDescription
limitnumber–Maximum number of examples to return. Default 3.
querystringyesChart type, feature, or use case (e.g. 'bar chart', 'donut', 'tooltip', 'sankey').

No output schema declared.

No examples provided.

listSBChartAPIs ~134

Browse the SBChart2.0 API surface by section and/or category. Call with no argument to get sections and their categories; filter by section or category to narrow. Use to explore what chart types and options exist. ⚠️ SBChart2.0 코드/샘플 생성 시 서버 공통지침(표준 골격에서 출발 · chartConfig 리터럴 나열 · 요청 기능만 최소 적용) 준수 — 상세는 서버 instructions 참고.

NameTypeReqDescription
categorystring–Optionally filter to a specific category.
sectionstring–Optionally restrict to one section.

No output schema declared.

No examples provided.

searchSBChartAPI ~185

Search SBChart2.0 chart API and option documentation by keyword. Returns matching entries with name, section, summary, and syntax. Start here to find which option or chart type fits, then call getSBChartAPIDetail for full details or getSBChartExample for code. ⚠️ SBChart2.0 코드/샘플 생성 시 서버 공통지침(표준 골격에서 출발 · chartConfig 리터럴 나열 · 요청 기능만 최소 적용) 준수 — 상세는 서버 instructions 참고.

NameTypeReqDescription
limitnumber–Maximum number of results to return. Default 5.
querystringyesKeyword to search: a chart type, option, or feature (e.g. 'bar', 'tooltip', 'gantt', 'axis').
sectionstring–Optionally restrict results to one section.

No output schema declared.

No examples provided.

Install

How do I install the SBChart2.0 MCP server?

SBChart2.0 MCP is a hosted endpoint at https://softbowl.co.kr/mcp/sbchart2.do, 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 · softbowl.co.kr

# add to Claude Code
claude mcp add --transport http kr-co-softbowl-sbchart2 'https://softbowl.co.kr/mcp/sbchart2.do'
Common questions

What is the SBChart2.0 MCP server?

SBChart2.0 MCP is listed in the public MCP registry as kr.co.softbowl/sbchart2. Softbowl SBChart2.0 차트(chart) 라이브러리의 공식 API 문서를 검색해, AI가 정확한 차트 코드를 생성하도록 돕습니다. This page covers its hosted endpoint (https://softbowl.co.kr/mcp/sbchart2.do).

Is the SBChart2.0 MCP server safe to use?

SBChart2.0 MCP scores 71 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 SBChart2.0 MCP server expose?

SBChart2.0 MCP exposes 4 tools: searchSBChartAPI, getSBChartAPIDetail, listSBChartAPIs, getSBChartExample. Their descriptions and schemas cost roughly 641 tokens of context every time the server is loaded.

Does the SBChart2.0 MCP server require authentication?

No. We connected to SBChart2.0 MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SBChart2.0 MCP server still maintained?

SBChart2.0 MCP 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 SBChart2.0 MCP server?

VerifyMCP ran 11 checks on SBChart2.0 MCP, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about SBChart2.0 MCP: Authorization and HTTPS. 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.