
Prenica MCP server
Which MCP servers are Prenica's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry namejp.prenica/mcpverified in the MCP registry
The registry name sits under prenica.jp. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools6
- Server calls itselfprenica-mcp
- Server version0.67.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 396 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 4 of 6 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer439 ms
- Space in an agent's context≈ 556 tokensthe definitions of all its tools (6), which an agent carries on every turn
- Tool definitionsC · 72 of 100
- Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 4 of 6
- Not saying whether it only reads or can destroy: 6 of 6
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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更新日の新しい順に公開情報を一覧します。「最近どんな発表が出ているか」を検索語なしで確認する用途です。
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"prenica": {
"type": "http",
"url": "https://mcp.prenica.jp/"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http prenica https://mcp.prenica.jp/claude.ai, ChatGPT and other clients: add https://mcp.prenica.jp/ as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.