_ registry / mcp streamable-http · checked 2h ago

softbowl-mcp-server (sbchart)

https://softbowl.co.kr

Registry code: c5ec2b36fce94150

api record

# SBChart2.0 차트 작성 공통 규칙 (MCP 프롬프트용)

이 문서는 **환경(로컬 경로·파일 위치·작업일지 등)에 종속되지 않는**, 어디서든 적용 가능한

endpoint
https://softbowl.co.kr/mcp/sbchart2.do
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is softbowl-mcp-server (sbchart) live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is softbowl-mcp-server (sbchart) free to use?
Yes — the hub reached it with no key and no payment.
What tools does softbowl-mcp-server (sbchart) have?
4 tools: listSBChartAPIs, getSBChartAPIDetail, searchSBChartAPI, getSBChartExample.
Is softbowl-mcp-server (sbchart) safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 99.2%· all time 99.2%

latency
1,656ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 356 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search charting library api docs
  • get chart code examples
  • get details of a chart option
takes → gives
text → text, code
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 open 4 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • listSBChartAPIs reads open 5h ago

    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 참고.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "section": {
          "enum": [
            "charts",
            "maps",
            "samples"
          ],
          "type": "string",
          "description": "Optionally restrict to one section."
        },
        "category": {
          "type": "string",
          "description": "Optionally filter to a specific category."
        }
      }
    }
    arguments 19 lines
  • getSBChartAPIDetail reads open 5h ago

    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 참고.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Exact option/API name as shown in searchSBChartAPI results (e.g. 'barFormat', 'Gantt 차트 데이터 포맷')."
        }
      }
    }
    arguments 12 lines
  • searchSBChartAPI reads open 5h ago

    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 참고.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Maximum number of results to return. Default 5."
        },
        "query": {
          "type": "string",
          "description": "Keyword to search: a chart type, option, or feature (e.g. 'bar', 'tooltip', 'gantt', 'axis')."
        },
        "section": {
          "enum": [
            "charts",
            "maps",
            "samples"
          ],
          "type": "string",
          "description": "Optionally restrict results to one section."
        }
      }
    }
    arguments 25 lines
  • getSBChartExample reads open 16h ago

    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 참고.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Maximum number of examples to return. Default 3."
        },
        "query": {
          "type": "string",
          "description": "Chart type, feature, or use case (e.g. 'bar chart', 'donut', 'tooltip', 'sankey')."
        }
      }
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c5ec2b36fce94150.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c5ec2b36fce94150/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c5ec2b36fce94150/badge.svg)](https://brick.blue/agent/c5ec2b36fce94150?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.