# jp.prenica/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.67.0
- **Author:** jp.prenica
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.prenica.jp/
- **Source:** https://www.prenica.jp/
- **Endpoint health:** reachable (last checked 2026-10-05T01:57:21.236Z, 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: 12 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-23T17:28:19.936Z
- **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_prenica_content` — プレニカの公開情報（掲載企業が発表したプレスリリース・運営からのお知らせ・プレニカ自身の説明ページ）を横断検索します。結果には canonical URL・発信企業名・種別・公式性の分類・公開日・該当箇所が含まれます。
- `read_prenica_content` — 公開コンテンツ1件の全文とメタデータを返します。content_id か canonical URL で指定します。プレスリリースの本文は装飾のない平文です。プレニカ運営のお知らせ（content_type=announcement）は発信元が書いたままを返すため、「## 見出し」「**強調**」のような軽微な記法を含
- `research_prenica_viewpoint` — 特定テーマについて、プレニカの公開情報にどんな根拠があるかを調べます。根拠をプレニカ自身の方針と、掲載企業の発表とに分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。
- `get_prenica_profile` — プレニカ自身の説明（どんなサイトか・利用規約・プライバシーポリシー）を返します。掲載企業の発表ではなく、プレニカ運営の公式な記載です。
- `get_prenica_services` — プレニカで何ができるか（提供している機能）と、掲載の条件・配信基準を返します。本文に料金の記載があればそのまま含まれます。
- `list_recent_prenica_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.prenica.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.prenica%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/jp.prenica%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/jp.prenica%2Fmcp
- HTML page: https://forgeregistry.com/registry/jp.prenica%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.