プレニカ MCP
REMOTE · MCP.PRENICA.JP · SCANNED SEP 28
プレニカに掲載された企業のプレスリリースと運営情報を検索・取得できる読み取り専用サーバー。出典は 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 → 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 Usability56
- 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 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
How do I install the プレニカ MCP server?
プレニカ MCP is a hosted endpoint at https://mcp.prenica.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.prenica.jp
claude mcp add --transport http jp-prenica-mcp 'https://mcp.prenica.jp/'
{
"mcpServers": {
"jp-prenica-mcp": {
"url": "https://mcp.prenica.jp/"
}
}
} {
"servers": {
"jp-prenica-mcp": {
"type": "http",
"url": "https://mcp.prenica.jp/"
}
}
} [mcp_servers.jp-prenica-mcp] url = "https://mcp.prenica.jp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-prenica-mcp": {
"type": "remote",
"url": "https://mcp.prenica.jp/",
"enabled": true
}
}
} openclaw mcp add jp-prenica-mcp --url 'https://mcp.prenica.jp/' --transport streamable-http
mcp_servers:
jp-prenica-mcp:
url: "https://mcp.prenica.jp/" {
"McpServers": {
"jp-prenica-mcp": {
"Transport": "http",
"Url": "https://mcp.prenica.jp/"
}
}
} assistant mcp add jp-prenica-mcp -t streamable-http -u 'https://mcp.prenica.jp/'
{
"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.
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.
- 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
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
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 28 Sept 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 | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a781a6d8d2d2d09c0e32dea150c3fe47 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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_prenica_profile 企業プロフィール ~60
プレニカ自身の説明（どんなサイトか・利用規約・プライバシーポリシー）を返します。掲載企業の発表ではなく、プレニカ運営の公式な記載です。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prenica_services できること・掲載条件 ~58
プレニカで何ができるか（提供している機能）と、掲載の条件・配信基準を返します。本文に料金の記載があればそのまま含まれます。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_prenica_content 新着コンテンツ一覧 ~80
更新日の新しい順に公開情報を一覧します。「最近どんな発表が出ているか」を検索語なしで確認する用途です。
| 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）は発信元が書いたままを返すため、「## 見出し」「**強調**」のような軽微な記法を含むことがあります。その場合は記号をそのまま引用せず、見出し・強調として読んでください。
| 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" を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| max_evidence | integer | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
search_prenica_content 公開情報の検索 ~184
プレニカの公開情報（掲載企業が発表したプレスリリース・運営からのお知らせ・プレニカ自身の説明ページ）を横断検索します。結果には canonical URL・発信企業名・種別・公式性の分類・公開日・該当箇所が含まれます。
| 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.
What is the プレニカ MCP server?
プレニカ MCP is listed in the public MCP registry as jp.prenica/mcp. プレニカに掲載された企業のプレスリリースと運営情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。 This page covers its hosted endpoint (https://mcp.prenica.jp/).
Is the プレニカ MCP server safe to use?
プレニカ MCP scores 69 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 プレニカ MCP server expose?
プレニカ MCP exposes 6 tools: search_prenica_content, read_prenica_content, research_prenica_viewpoint, get_prenica_profile, get_prenica_services, list_recent_prenica_content. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.
Does the プレニカ MCP server require authentication?
No. We connected to プレニカ MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the プレニカ MCP server still maintained?
プレニカ MCP is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.