プレニカ MCP

REMOTE · MCP.PRENICA.JP · SCANNED AUG 9

プレニカに掲載された企業のプレスリリースと運営情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。

Available components

52 52 Trust /100

Trust breakdown (6 categories)

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 Usability48

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 1842 tokens (~307/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 Management3

Stability observed for 1 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

Install

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.prenica.jp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http jp-prenica-mcp https://mcp.prenica.jp/

# ~/.codex/config.toml

[mcp_servers.jp-prenica-mcp]
url = "https://mcp.prenica.jp/"

// opencode.json

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

# add to OpenClaw

openclaw mcp add jp-prenica-mcp --url https://mcp.prenica.jp/ --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  jp-prenica-mcp:
    url: "https://mcp.prenica.jp/"

// mcp.json

{
  "mcpServers": {
    "jp-prenica-mcp": {
      "type": "http",
      "url": "https://mcp.prenica.jp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog Show cosmetic changes

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.

9 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “read_prenica_content” rewrote its description, which is the text the model reads security
- Schema quality: 228 → 307 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.18.1 → 0.65.0 functional
- Tool “read_prenica_content” changed its title: 公式コンテンツの全文取得 → 公開コンテンツの全文取得 cosmetic
- Tool “search_prenica_content” changed its title: 公式情報の検索 → 公開情報の検索 cosmetic
8 Aug 26 52

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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.prenica.jp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=prenica.jp	CN=WE1,O=Google Trust Services,C=US	6 Jul 2026	4 Oct 2026	ECDSA 256	ECDSA-SHA256	813a30a5432417ff134956d8c4861cd7
SANs: prenica.jp, *.prenica.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.prenica.jp. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
jp.	present	33631	8	Verified
prenica.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.prenica.jp/	Verified	200
http (plaintext)	http://mcp.prenica.jp/	Served over HTTP	200

MCP tools · 6 exposed · ~638 tokens

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.

Tool Tokens

get_prenica_profile 企業プロフィール ~60

プレニカ自身の説明（どんなサイトか・利用規約・プライバシーポリシー）を返します。掲載企業の発表ではなく、プレニカ運営の公式な記載です。

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_prenica_services できること・掲載条件 ~58

プレニカで何ができるか（提供している機能）と、掲載の条件・配信基準を返します。本文に料金の記載があればそのまま含まれます。

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_recent_prenica_content 新着コンテンツ一覧 ~80

更新日の新しい順に公開情報を一覧します。「最近どんな発表が出ているか」を検索語なしで確認する用途です。

Input Output Examples

Name	Type	Req	Description
content_types	array	–	–
limit	integer	–	–
since	string	–	この日付以降に更新されたもの (YYYY-MM-DD)。

No output schema declared.

No examples provided.

read_prenica_content 公開コンテンツの全文取得 ~155

公開コンテンツ1件の全文とメタデータを返します。content_id か canonical URL で指定します。プレスリリースの本文は装飾のない平文です。プレニカ運営のお知らせ（content_type=announcement）は発信元が書いたままを返すため、「## 見出し」「**強調**」のような軽微な記法を含むことがあります。その場合は記号をそのまま引用せず、見出し・強調として読んでください。

Input Output Examples

Name	Type	Req	Description
content_id	string	–	–
max_chars	integer	–	–
url	string	–	–

No output schema declared.

No examples provided.

research_prenica_viewpoint テーマ別の見解調査 ~101

特定テーマについて、プレニカの公開情報にどんな根拠があるかを調べます。根拠をプレニカ自身の方針と、掲載企業の発表とに分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。

Input Output Examples

Name	Type	Req	Description
max_evidence	integer	–	–
topic	string	yes	–

No output schema declared.

No examples provided.

search_prenica_content 公開情報の検索 ~184

プレニカの公開情報（掲載企業が発表したプレスリリース・運営からのお知らせ・プレニカ自身の説明ページ）を横断検索します。結果には canonical URL・発信企業名・種別・公式性の分類・公開日・該当箇所が含まれます。

Input Output Examples

Name	Type	Req	Description
content_types	array	–	絞り込むコンテンツ種別。
issuer	string	–	発信した企業名の部分一致（プレスリリースのみ）。
limit	integer	–	–
published_from	string	–	公開日の下限 (YYYY-MM-DD)。
published_to	string	–	公開日の上限 (YYYY-MM-DD)。
query	string	yes	検索クエリ。日本語可。

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

8 Aug 9 Aug