# jp.co.contencial/mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.2.0
- **Author:** jp.co.contencial
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.contencial.co.jp/
- **Source:** https://seo.contencial.co.jp/mcp/
- **Endpoint health:** reachable (last checked 2026-10-04T23:06:04.430Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 13 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-23T12:12:42.780Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

6 declared. Observed from a live `tools/list` probe.
- `search_contencial_content` — 株式会社コンテンシャルの公開情報（会社概要・経営方針・メンバー・サービス・SEOブログ・SEOレポート・取り組み事例・お知らせ）を横断検索します。結果には canonical URL・種別・公式性の分類・更新日・該当箇所が含まれます。
- `read_contencial_content` — 公開コンテンツ1件の全文とメタデータを返します。content_id か canonical URL で指定します。
- `research_contencial_viewpoint` — 特定テーマに対するコンテンシャルの考え方を調べます。根拠を公式方針／サービス説明／専門記事／代表者見解に分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。
- `get_contencial_profile` — 会社概要・経営方針・代表挨拶・代表者プロフィール・運営ポリシー・アクセス・採用情報と、メンバー一覧・取り組み事例一覧を返します。
- `get_contencial_services` — 提供サービスの一覧と各サービスの公式説明・canonical URL を返します。本文に料金やプランの記載があればそのまま含まれます。
- `list_recent_contencial_content` — 更新日の新しい順に公式コンテンツを一覧します。「最近どんな発信をしているか」を検索語なしで確認する用途です。

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.contencial.co.jp/\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/jp.co.contencial%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/jp.co.contencial%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/jp.co.contencial%2Fmcp
- HTML page: https://forgeregistry.com/registry/jp.co.contencial%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.