Contencial MCP
REMOTE · MCP.CONTENCIAL.CO.JP
株式会社コンテンシャルの公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。
Available components
Last scanned (16 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Usability65
- AI-judged instruction clarity (good).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 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 8 Nov 26 +1
- Stability: 0.97 → pass security
- 7 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 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
- 5 Sept 26 0
- Stability: 0.97 → pass security
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 21 Nov 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 | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 615ea3ce6055e39f137237297c3d0529 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.contencial.co.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | DS published | 6961 | 8 | Verified |
| co.jp. | No DS | Delegated | ||
| contencial.co.jp. | No DS | 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.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. 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_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.
How do I install the Contencial MCP server?
Contencial MCP is a hosted endpoint at https://mcp.contencial.co.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.contencial.co.jp
claude mcp add --transport http jp-co-contencial-mcp 'https://mcp.contencial.co.jp/'
What is the Contencial MCP server?
Contencial MCP is listed in the public MCP registry as jp.co.contencial/mcp. 株式会社コンテンシャルの公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。 This page covers its hosted endpoint (https://mcp.contencial.co.jp/).
Is the Contencial MCP server safe to use?
Contencial MCP scores 71 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 Contencial MCP server expose?
Contencial MCP exposes 6 tools: search_contencial_content, read_contencial_content, research_contencial_viewpoint, get_contencial_profile, get_contencial_services, list_recent_contencial_content. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.
Does the Contencial MCP server require authentication?
No. We connected to Contencial MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Contencial MCP server still maintained?
Contencial MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Contencial MCP server?
VerifyMCP ran 12 checks on Contencial MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Contencial MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.