UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback)
REMOTE · SHONANFARM.COM · SCANNED SEP 22
バイクを売りたい方へ。中古バイク・原付・スクーターの買取相場照会と無料出張査定の申込。対応=神奈川・東京・埼玉・千葉・茨城・群馬・山梨。Japan used motorcycle buyback.
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1325 tokens (~441/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) MCP server?
UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) is a hosted endpoint at https://shonanfarm.com/wp-json/zama/v1/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 · shonanfarm.com
claude mcp add --transport http com-shonanfarm-zama-bike-kaitori 'https://shonanfarm.com/wp-json/zama/v1/mcp'
{
"mcpServers": {
"com-shonanfarm-zama-bike-kaitori": {
"url": "https://shonanfarm.com/wp-json/zama/v1/mcp"
}
}
} {
"servers": {
"com-shonanfarm-zama-bike-kaitori": {
"type": "http",
"url": "https://shonanfarm.com/wp-json/zama/v1/mcp"
}
}
} [mcp_servers.com-shonanfarm-zama-bike-kaitori] url = "https://shonanfarm.com/wp-json/zama/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-shonanfarm-zama-bike-kaitori": {
"type": "remote",
"url": "https://shonanfarm.com/wp-json/zama/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-shonanfarm-zama-bike-kaitori --url 'https://shonanfarm.com/wp-json/zama/v1/mcp' --transport streamable-http
mcp_servers:
com-shonanfarm-zama-bike-kaitori:
url: "https://shonanfarm.com/wp-json/zama/v1/mcp" {
"McpServers": {
"com-shonanfarm-zama-bike-kaitori": {
"Transport": "http",
"Url": "https://shonanfarm.com/wp-json/zama/v1/mcp"
}
}
} assistant mcp add com-shonanfarm-zama-bike-kaitori -t streamable-http -u 'https://shonanfarm.com/wp-json/zama/v1/mcp'
{
"mcpServers": {
"com-shonanfarm-zama-bike-kaitori": {
"type": "http",
"url": "https://shonanfarm.com/wp-json/zama/v1/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.
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.97 ▲ functional
- 3 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 6 Aug 26 0
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.37 ▲ functional
- 5 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.30 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 22 Sept 2026 · Probed https://shonanfarm.com/wp-json/zama/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shonanfarm.com | CN=YR1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 2048 | SHA256-RSA | 5645bdc0853ecc34b05d395f99c5d029149 |
| SANs: shonanfarm.com, www.shonanfarm.com | ||||||
| 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 shonanfarm.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| shonanfarm.com. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shonanfarm.com/wp-json/zama/v1/mcp | Verified | 200 | |
| http (plaintext) | http://shonanfarm.com/wp-json/zama/v1/mcp | HTTPS enforced | 302 | https://shonanfarm.com/wp-json/zama/v1/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_price ~227
中古バイク・原付・スクーターを売りたいユーザーに、車種と車両状態別の出張買取の概算相場（円）を返す。ユーザーが「いくらになる／相場は／売ったらいくら／査定して／高く売りたい／バイクを処分したい／乗らなくなった／不動車や事故車でも売れる?」等と尋ねた時に使う。相場の提示のみで、実際の買取申込は行わない（申込は submit_kaitori_request を使う）。車種が特定できない場合は先に search_models で正式表記を確定すること。
| Name | Type | Req | Description |
|---|---|---|---|
| maker | string | – | メーカー名（任意。同名車種の絞り込み用。例: ホンダ／ヤマハ） |
| model | string | yes | 車種名（search_modelsの結果の正式表記をそのまま渡す） |
No output schema declared.
No examples provided.
search_models ~193
ユーザーが挙げたメーカー名・車名・型式・排気量から、買取査定に対応する正式なバイク車種名を検索・特定する。「CB400」「125のスクーター」「ジャイロ」「4ミニ」「原付」のような曖昧・部分的な入力を正規の車種表記に解決するために使う。相場や金額は返さない（相場は get_price を使う）。get_price を呼ぶ前に、必ずこれで正確な車種名を確定すること。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 車種名・メーカー名・型式・排気量の一部（日本語/英数字可。例:「ジャイロ」「PCX」「ホンダ」「JBK-JF56」） |
No output schema declared.
No examples provided.
submit_kaitori_request ~617
ユーザーがバイク・原付・スクーターの出張買取を実際に申し込む意思を示した時（「売りたい／申し込みたい／来てほしい／査定に来て／引き取ってほしい／廃車にしたい／処分したい」等）に、氏名・電話番号・エリア・車種を受け取り、無料の出張買取を申し込む。単に相場を知りたいだけの段階では使わず、その場合は get_price を使うこと。希望の査定日時があれば preferred_1〜3 に第3希望まで入れてよい（任意）。【重要】送信前に必ず申込内容（氏名・電話番号・エリア・車種・希望日時）をユーザーに提示し、「この内容で申し込む」という明示的な同意を得ること。同意を得た場合のみ confirm を true にする。confirm が true でない場合は送信されず、内容確認用のプレビューが返る。ユーザー本人の氏名・電話番号のみ使用可。
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | バイクの所在エリア。都道府県＋市区町村まで（例: 神奈川県座間市） |
| condition | string | – | 車両の状態（任意。例: 動作可・良好／エンジン不動／事故車／書類なし・鍵なし） |
| confirm | boolean | yes | ユーザーに申込内容を提示して明示的な同意を得た場合のみ true。未確認なら false（プレビューが返る） |
| model | string | yes | 車種名（例: ジャイロ(X/キャノピー)。不明なら分かる範囲でよい） |
| name | string | yes | ユーザー本人の氏名（例: 山田太郎） |
| notes | string | – | 補足・希望連絡時間帯など（任意） |
| phone | string | yes | 連絡先の電話番号（日本の番号。例: 090-1234-5678） |
| preferred_1 | string | – | 査定に来てほしい日時の第1希望（任意。例: 8月1日(土) 午前）。時間帯は午前／午後／夕方の粒度でよい |
| preferred_2 | string | – | 第2希望（任意。書式は preferred_1 と同じ） |
| preferred_3 | string | – | 第3希望（任意。書式は preferred_1 と同じ） |
| year | string | – | 年式（任意。西暦。例: 2015、不明でも可） |
No output schema declared.
No examples provided.
What is the UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) MCP server?
UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) is an MCP server listed in the public MCP registry as com.shonanfarm/zama-bike-kaitori. バイクを売りたい方へ。中古バイク・原付・スクーターの買取相場照会と無料出張査定の申込。対応=神奈川・東京・埼玉・千葉・茨城・群馬・山梨。Japan used motorcycle buyback. This page covers its hosted endpoint (https://shonanfarm.com/wp-json/zama/v1/mcp).
Is the UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) MCP server safe to use?
UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) scores 81 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 UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) MCP server expose?
UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) exposes 3 tools: search_models, get_price, submit_kaitori_request. Their descriptions and schemas cost roughly 1,037 tokens of context every time the server is loaded.
Does the UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) MCP server require authentication?
No. We connected to UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) MCP server still maintained?
UsedBikeCenter ZAMA バイク・原付の買取査定 (Japan motorcycle buyback) is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.