株式会社コンテンシャル
REMOTE · MCP.YOMITASU.JP
SEO 対策とサイト改善を手がける株式会社コンテンシャルの公式サイトです。（seo.contencial.co.jp の内容を検索して答える。ヨミタス経由）
Available components
Last scanned (3 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Marketing and SEO
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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 870 tokens (~145/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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 23 Oct 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 43. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 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.
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 23 Oct 2026 · Probed https://mcp.yomitasu.jp/s/seo-contencial-co-jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yomitasu.jp | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4a1447d8f9e4e0b10e3615b5ae9f0732 |
| SANs: yomitasu.jp, *.yomitasu.jp | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.yomitasu.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| yomitasu.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.yomitasu.jp/s/seo-contencial-co-jp/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.yomitasu.jp/s/seo-contencial-co-jp/mcp | HTTPS enforced | 301 | https://mcp.yomitasu.jp/s/seo-contencial-co-jp/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 →
fetch ページの中身を読む ~109
「株式会社コンテンシャル」のページの本文を、最初から最後まで返します。search で見つけたサービスの内容、支援事例の取り組み、お知らせの詳細、SEO Note!! の記事や月ごとのレポートをくわしく読むときに使います。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 探した結果の id（ページの URL）。ページの URL かパスでも可（日本語のままでも可） |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_page ページの中身を読む（以前の名前） ~99
「株式会社コンテンシャル」（seo.contencial.co.jp）の以前の名前の機能です（すでにつないでいる人のために残しています）。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | ページの URL かパス（日本語のままでも可） |
No output schema declared.
No examples provided.
list_pages どんなページがあるか見る ~130
「株式会社コンテンシャル」に読み込まれているページの一覧（タイトルと URL）を返します。/service/ はサービス、/casestudy/ は支援事例、/news/ はお知らせ、/seo-note/ は SEO Note!!（/seo-note/report/ が月ごとの振り返り）、/company/ は会社情報、/tag/ は記事のタグ別の一覧です。事例やお知らせをまとめて挙げたいときに使います。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
search サイトの中を探す ~172
「株式会社コンテンシャル」（SEO 対策の会社）の公式サイトから、言葉に当てはまる箇所を抜粋つきで探します。事業とサービスの内容（SEO コンサルティング、WEB 広告など）、支援事例、特許・連載・提携などのお知らせ、SEO メディア「SEO Note!!」の解説記事と毎月の SEO 振り返りレポートを探せます。この会社やサービスについて質問されたら、まずこれを使ってください。「特許」「2026年8月 レポート」のように短い言葉で探します。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 探したい言葉（例: 料金 支払い方法） |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| results | array | yes | – |
No examples provided.
search_pages サイトの中を探す（以前の名前） ~104
「株式会社コンテンシャル」（seo.contencial.co.jp）の以前の名前の機能です（すでにつないでいる人のために残しています）。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | 探したい言葉（例: 料金 支払い方法） |
No output schema declared.
No examples provided.
site_overview サイトの概要を知る ~96
「株式会社コンテンシャル」の概要を返します。代表取締役の柏崎剛のもとで、SEO 対策とサイト改善のコンサルティング、ツール開発、SEO メディアの運営を手がける会社の公式サイトです。どんな会社か、何を頼めるかを最初に知りたいときに使います。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the 株式会社コンテンシャル MCP server?
株式会社コンテンシャル is a hosted endpoint at https://mcp.yomitasu.jp/s/seo-contencial-co-jp/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 · mcp.yomitasu.jp
claude mcp add --transport http jp-yomitasu-seo-contencial-co-jp 'https://mcp.yomitasu.jp/s/seo-contencial-co-jp/mcp'
What is the 株式会社コンテンシャル MCP server?
株式会社コンテンシャル is an MCP server listed in the public MCP registry as jp.yomitasu/seo-contencial-co-jp. SEO 対策とサイト改善を手がける株式会社コンテンシャルの公式サイトです。（seo.contencial.co.jp の内容を検索して答える。ヨミタス経由）. This page covers its hosted endpoint (https://mcp.yomitasu.jp/s/seo-contencial-co-jp/mcp).
Is the 株式会社コンテンシャル MCP server safe to use?
株式会社コンテンシャル 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 株式会社コンテンシャル MCP server expose?
株式会社コンテンシャル exposes 6 tools: search, fetch, list_pages, site_overview, search_pages, get_page. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.
Does the 株式会社コンテンシャル MCP server require authentication?
No. We connected to 株式会社コンテンシャル without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 株式会社コンテンシャル MCP server still maintained?
株式会社コンテンシャル is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.