# Contencial MCP (remote · mcp.contencial.co.jp)

株式会社コンテンシャルの公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-09

## Components

- remote · `mcp.contencial.co.jp`: 56/100 (this document), [markdown](https://verifymcp.io/servers/jp-co-contencial-mcp/mcp.md), [page](https://verifymcp.io/servers/jp-co-contencial-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.contencial.co.jp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-09.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http jp-co-contencial-mcp https://mcp.contencial.co.jp/
```

### Codex

```toml
[mcp_servers.jp-co-contencial-mcp]
url = "https://mcp.contencial.co.jp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jp-co-contencial-mcp": {
      "type": "remote",
      "url": "https://mcp.contencial.co.jp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jp-co-contencial-mcp --url https://mcp.contencial.co.jp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jp-co-contencial-mcp:
    url: "https://mcp.contencial.co.jp/"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-08 (score 56, +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.

### 2026-08-07 (score 55, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-06 (score 55)

First indexed and scored.

## MCP tools (6)

### `search_contencial_content` (~180 tokens)

公式情報の検索

株式会社コンテンシャルの公開情報（会社概要・経営方針・メンバー・サービス・SEOブログ・SEOレポート・取り組み事例・お知らせ）を横断検索します。結果には canonical URL・種別・公式性の分類・更新日・該当箇所が含まれます。

Input parameters:

- `author` (string): 著者名の部分一致。
- `content_types` (array): 絞り込むコンテンツ種別。
- `limit` (integer)
- `published_from` (string): 公開日の下限 (YYYY-MM-DD)。
- `published_to` (string): 公開日の上限 (YYYY-MM-DD)。
- `query` (string, required): 検索クエリ。日本語可。

### `read_contencial_content` (~62 tokens)

公式コンテンツの全文取得

公開コンテンツ1件の全文とメタデータを返します。content_id か canonical URL で指定します。

Input parameters:

- `content_id` (string)
- `max_chars` (integer)
- `url` (string)

### `research_contencial_viewpoint` (~93 tokens)

テーマ別の見解調査

特定テーマに対するコンテンシャルの考え方を調べます。根拠を公式方針／サービス説明／専門記事／代表者見解に分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。

Input parameters:

- `max_evidence` (integer)
- `topic` (string, required)

### `get_contencial_profile` (~59 tokens)

企業プロフィール

会社概要・経営方針・代表挨拶・代表者プロフィール・運営ポリシー・アクセス・採用情報と、メンバー一覧・取り組み事例一覧を返します。

### `get_contencial_services` (~48 tokens)

サービス一覧

提供サービスの一覧と各サービスの公式説明・canonical URL を返します。本文に料金やプランの記載があればそのまま含まれます。

### `list_recent_contencial_content` (~80 tokens)

新着コンテンツ一覧

更新日の新しい順に公式コンテンツを一覧します。「最近どんな発信をしているか」を検索語なしで確認する用途です。

Input parameters:

- `content_types` (array)
- `limit` (integer)
- `since` (string): この日付以降に更新されたもの (YYYY-MM-DD)。

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jp-co-contencial-mcp/mcp#diagnostics

## Score history

- 2026-08-09: 56
- 2026-08-08: 56
- 2026-08-07: 55
- 2026-08-06: 55

## Links

- Remote endpoint: https://mcp.contencial.co.jp/
- Website: https://seo.contencial.co.jp/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/jp-co-contencial-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jp-co-contencial-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/jp-co-contencial-mcp/mcp