Contencial MCP
REMOTE · MCP.CONTENCIAL.CO.JP · SCANNED AUG 9
株式会社コンテンシャルの公開情報を検索・取得できる読み取り専用サーバー。出典は 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 →
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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1206 tokens (~201/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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (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 · mcp.contencial.co.jp
claude mcp add --transport http jp-co-contencial-mcp https://mcp.contencial.co.jp/
[mcp_servers.jp-co-contencial-mcp] url = "https://mcp.contencial.co.jp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-co-contencial-mcp": {
"type": "remote",
"url": "https://mcp.contencial.co.jp/",
"enabled": true
}
}
} openclaw mcp add jp-co-contencial-mcp --url https://mcp.contencial.co.jp/ --transport streamable-http
mcp_servers:
jp-co-contencial-mcp:
url: "https://mcp.contencial.co.jp/" {
"mcpServers": {
"jp-co-contencial-mcp": {
"type": "http",
"url": "https://mcp.contencial.co.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.
- 8 Aug 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.
- 7 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 6 Aug 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 9 Aug 2026 · Probed https://mcp.contencial.co.jp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=contencial.co.jp | CN=WE1,O=Google Trust Services,C=US | 26 Jun 2026 | 24 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 98827e92803b819f1309750ec0fac90c |
| SANs: contencial.co.jp, *.contencial.co.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 |
DNSSEC insecure
Validation of mcp.contencial.co.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| co.jp. | absent | Delegated | ||
| contencial.co.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.contencial.co.jp/ | Verified | 200 | |
| http (plaintext) | http://mcp.contencial.co.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.
get_contencial_profile 企業プロフィール ~59
会社概要・経営方針・代表挨拶・代表者プロフィール・運営ポリシー・アクセス・採用情報と、メンバー一覧・取り組み事例一覧を返します。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_contencial_services サービス一覧 ~48
提供サービスの一覧と各サービスの公式説明・canonical URL を返します。本文に料金やプランの記載があればそのまま含まれます。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_contencial_content 新着コンテンツ一覧 ~80
更新日の新しい順に公式コンテンツを一覧します。「最近どんな発信をしているか」を検索語なしで確認する用途です。
| Name | Type | Req | Description |
|---|---|---|---|
| content_types | array | – | – |
| limit | integer | – | – |
| since | string | – | この日付以降に更新されたもの (YYYY-MM-DD)。 |
No output schema declared.
No examples provided.
read_contencial_content 公式コンテンツの全文取得 ~62
公開コンテンツ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_contencial_viewpoint テーマ別の見解調査 ~93
特定テーマに対するコンテンシャルの考え方を調べます。根拠を公式方針／サービス説明／専門記事／代表者見解に分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| max_evidence | integer | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
search_contencial_content 公式情報の検索 ~180
株式会社コンテンシャルの公開情報（会社概要・経営方針・メンバー・サービス・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.