SEO対策研究室 MCP
REMOTE · MCP.TSUYOSHIKASHIWAZAKI.JP · SCANNED SEP 28
SEO対策研究室（柏崎剛）の公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。
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 Security46
- 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 6 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1365 tokens (~227/item across 6 items; 6 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 Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SEO対策研究室 MCP server?
SEO対策研究室 MCP is a hosted endpoint at https://mcp.tsuyoshikashiwazaki.jp/, 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 · mcp.tsuyoshikashiwazaki.jp
claude mcp add --transport http jp-tsuyoshikashiwazaki-mcp 'https://mcp.tsuyoshikashiwazaki.jp/'
{
"mcpServers": {
"jp-tsuyoshikashiwazaki-mcp": {
"url": "https://mcp.tsuyoshikashiwazaki.jp/"
}
}
} {
"servers": {
"jp-tsuyoshikashiwazaki-mcp": {
"type": "http",
"url": "https://mcp.tsuyoshikashiwazaki.jp/"
}
}
} [mcp_servers.jp-tsuyoshikashiwazaki-mcp] url = "https://mcp.tsuyoshikashiwazaki.jp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-tsuyoshikashiwazaki-mcp": {
"type": "remote",
"url": "https://mcp.tsuyoshikashiwazaki.jp/",
"enabled": true
}
}
} openclaw mcp add jp-tsuyoshikashiwazaki-mcp --url 'https://mcp.tsuyoshikashiwazaki.jp/' --transport streamable-http
mcp_servers:
jp-tsuyoshikashiwazaki-mcp:
url: "https://mcp.tsuyoshikashiwazaki.jp/" {
"McpServers": {
"jp-tsuyoshikashiwazaki-mcp": {
"Transport": "http",
"Url": "https://mcp.tsuyoshikashiwazaki.jp/"
}
}
} assistant mcp add jp-tsuyoshikashiwazaki-mcp -t streamable-http -u 'https://mcp.tsuyoshikashiwazaki.jp/'
{
"mcpServers": {
"jp-tsuyoshikashiwazaki-mcp": {
"type": "http",
"url": "https://mcp.tsuyoshikashiwazaki.jp/"
}
}
} 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.
- 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
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 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
- 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
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 28 Sept 2026 · Probed https://mcp.tsuyoshikashiwazaki.jp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.tsuyoshikashiwazaki.jp | CN=YR1,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | RSA 2048 | SHA256-RSA | 60735e71604d964618e61067a22aa250ed7 |
| SANs: mcp.tsuyoshikashiwazaki.jp | ||||||
| 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 mcp.tsuyoshikashiwazaki.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| tsuyoshikashiwazaki.jp. | 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://mcp.tsuyoshikashiwazaki.jp/ | Verified | 200 | |
| http (plaintext) | http://mcp.tsuyoshikashiwazaki.jp/ | Served over HTTP | 200 |
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_tsuyoshikashiwazaki_profile サイト・運営者プロフィール ~51
サイト概要・サイト責任者（柏崎剛）のプロフィール・プライバシーポリシーと、検証事例一覧を返します。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tsuyoshikashiwazaki_services 取り組み一覧 ~42
業種別SEO・教育SEO等の取り組みページの一覧と各説明・canonical URL を返します。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_tsuyoshikashiwazaki_content 新着コンテンツ一覧 ~86
更新日の新しい順に公式コンテンツを一覧します。「最近どんな発信をしているか」を検索語なしで確認する用途です。
| Name | Type | Req | Description |
|---|---|---|---|
| content_types | array | – | – |
| limit | integer | – | – |
| since | string | – | この日付以降に更新されたもの (YYYY-MM-DD)。 |
No output schema declared.
No examples provided.
read_tsuyoshikashiwazaki_content 公式コンテンツの全文取得 ~68
公開コンテンツ1件の全文とメタデータを返します。content_id か canonical URL で指定します。
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | – | – |
| max_chars | integer | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
research_tsuyoshikashiwazaki_viewpoint テーマ別の見解調査 ~118
特定テーマに対する SEO対策研究室（サイト責任者: 柏崎剛）の考え方・解説を調べます。根拠をサイトポリシー／取り組み説明／解説記事／運営者見解に分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| max_evidence | integer | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
search_tsuyoshikashiwazaki_content 公式情報の検索 ~217
SEO対策研究室（運営: 株式会社コンテンシャル / サイト責任者: 柏崎剛、www.tsuyoshikashiwazaki.jp）の公開情報（SEO解説記事・用語辞典・検証事例・業種別SEOの取り組み・運営者プロフィール・お知らせ）を横断検索します。結果には canonical URL・種別・情報源の分類・更新日・該当箇所が含まれます。
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | 著者名の部分一致。 |
| content_types | array | – | 絞り込むコンテンツ種別。 |
| limit | integer | – | – |
| published_from | string | – | 公開日の下限 (YYYY-MM-DD)。 |
| published_to | string | – | 公開日の上限 (YYYY-MM-DD)。 |
| query | string | yes | 検索クエリ。日本語可。 |
No output schema declared.
No examples provided.
What is the SEO対策研究室 MCP server?
SEO対策研究室 MCP is listed in the public MCP registry as jp.tsuyoshikashiwazaki/mcp. SEO対策研究室（柏崎剛）の公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。 This page covers its hosted endpoint (https://mcp.tsuyoshikashiwazaki.jp/).
Is the SEO対策研究室 MCP server safe to use?
SEO対策研究室 MCP scores 70 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 SEO対策研究室 MCP server expose?
SEO対策研究室 MCP exposes 6 tools: search_tsuyoshikashiwazaki_content, read_tsuyoshikashiwazaki_content, research_tsuyoshikashiwazaki_viewpoint, get_tsuyoshikashiwazaki_profile, get_tsuyoshikashiwazaki_services, list_recent_tsuyoshikashiwazaki_content. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.
Does the SEO対策研究室 MCP server require authentication?
No. We connected to SEO対策研究室 MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEO対策研究室 MCP server still maintained?
SEO対策研究室 MCP is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.