Hokyo MCP Server
REMOTE · BUSTUP-MONITOR.COM · SCANNED AUG 3
豊胸モニター募集サイトのMCPサーバー。クリニック検索・術式情報・悩み相談・世代別記事を提供します。
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 →
Endpoint Security49
- 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 10 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability49
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 898 tokens (~44/item across 20 items; 10 tools + 10 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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · bustup-monitor.com
claude mcp add --transport http com-bustup-monitor-mcp https://bustup-monitor.com/mcp
[mcp_servers.com-bustup-monitor-mcp] url = "https://bustup-monitor.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bustup-monitor-mcp": {
"type": "remote",
"url": "https://bustup-monitor.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-bustup-monitor-mcp --url https://bustup-monitor.com/mcp --transport streamable-http
mcp_servers:
com-bustup-monitor-mcp:
url: "https://bustup-monitor.com/mcp" {
"mcpServers": {
"com-bustup-monitor-mcp": {
"type": "http",
"url": "https://bustup-monitor.com/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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 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 Jul 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.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 55
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 3 Aug 2026 · Probed https://bustup-monitor.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bustup-monitor.com | CN=WE1,O=Google Trust Services,C=US | 3 Jul 2026 | 1 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | f287153f0deebf880e9faaeebe21d28e |
| SANs: bustup-monitor.com, *.bustup-monitor.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of bustup-monitor.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bustup-monitor.com. | present | 2371 | 13 | Verified |
| bustup-monitor.com. | Verified address RRset verified with the apex keys |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bustup-monitor.com/mcp | Verified | 200 | |
| http (plaintext) | http://bustup-monitor.com/mcp | Inconclusive | 406 |
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.
get_article_by_slug ~42
スラグを指定して世代別記事を取得します。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 記事スラグ（例: elegant-aging） |
No output schema declared.
No examples provided.
get_clinic_detail ~115
指定したクリニックの詳細情報を取得します。各ブランチの住所だけでなく、駅からのアクセス（出口・徒歩分・タクシー・バス・行き方の目印）も含まれます。
| Name | Type | Req | Description |
|---|---|---|---|
| clinicId | string | yes | クリニックID（sbc, seishin, shibuya, tokyo, theclinic, ikeda, bell, garden, nagumo, isea, yokohama, mods-clinic） |
No output schema declared.
No examples provided.
get_clinics_by_area ~74
都道府県を指定してクリニックを検索します。該当する院の詳細（院名・住所・駅アクセス）も含めて返します。
| Name | Type | Req | Description |
|---|---|---|---|
| prefecture | string | yes | 都道府県名（例: 東京都、大阪府、福岡県） |
No output schema declared.
No examples provided.
get_complication_detail ~101
指定した合併症の詳細情報（定義・メカニズム・統計・予防・治療・FAQ・引用文献）を取得します。
| Name | Type | Req | Description |
|---|---|---|---|
| complicationId | string | yes | 合併症ID（capsular-contracture, infection, fat-necrosis, bia-alcl, vascular-embolism, fat-embolism, seroma, implant-rupture, malposition, allergy） |
No output schema declared.
No examples provided.
get_concern_detail ~77
指定した悩みの詳細情報を取得します。
| Name | Type | Req | Description |
|---|---|---|---|
| concernId | string | yes | 悩みID（small-breasts, breast-sagging, post-pregnancy-and-diet, breast-asymmetry, wide-set-breasts, body-proportions, nipple-darkening, choosing-underware） |
No output schema declared.
No examples provided.
get_guide_article_by_slug ~66
スラグを指定してクリニック選びガイドの記事を取得します。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 記事スラグ（例: choosing-by-price, revision-surgery-reality, dangerous-clinic-signs, post-op-aftercare） |
No output schema declared.
No examples provided.
get_postop_guide ~95
豊胸術後の経過ガイド（正常範囲・医学的機序・要注意サイン・推奨アクション）を取得します。症状名でフィルタ可能。
| Name | Type | Req | Description |
|---|---|---|---|
| symptom | string | — | 症状名（pain, swelling, fever, redness, lump, hardness, sensation, asymmetry）。省略すると全症状を返す。 |
No output schema declared.
No examples provided.
get_procedure_detail ~57
指定した術式の詳細情報を取得します。
| Name | Type | Req | Description |
|---|---|---|---|
| procedureId | string | yes | 術式ID（hyaluronic, breast-implants, fat-transfer, condensed-rich-fat-grafting, stem-cell-transfer） |
No output schema declared.
No examples provided.
get_report_by_slug ~80
スラグを指定して編集部レポートを取得します（個人を特定しない形でSNSの声を集約した第三者レポート）。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | レポートスラグ（例: hyaluronic-acid-real-voices, fat-transfer-long-term, monitor-reality-report） |
No output schema declared.
No examples provided.
search_clinics ~147
条件に合うクリニックを検索します。エリア（都道府県または地方名）と術式で絞り込めます。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | — | クリニック名や説明文での部分検索 |
| prefecture | string | — | 都道府県名（例: 東京都、大阪府） |
| procedure | string | — | 術式名（例: ヒアルロン酸、バッグ挿入、脂肪注入） |
| region | string | — | 地方名（例: 関東、関西、九州）。prefectureより優先度が低い |
No output schema declared.
No examples provided.