Remote MCP · Endpoint

Prenica(プレニカ) MCP server

No. Prenica(プレニカ) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.yomitasu.jp/s/prenica-jp/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/prenica-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
642 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
無料でしっかり使える、審査制のプレスリリース配信サービスです。(prenica.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of Prenica(プレニカ)
CheckedResultHandshake
1 hour agoHandshake completed642 ms
1 day agoHandshake completed2.29 s
4 days agoHandshake completed620 ms
6 days agoHandshake completed652 ms
7 days agoHandshake completed663 ms
9 days agoHandshake completed631 ms
10 days agoHandshake completed1.18 s
11 days agoHandshake completed609 ms
14 days agoHandshake completed648 ms
15 days agoHandshake completed659 ms
17 days agoHandshake completed603 ms
19 days agoHandshake completed622 ms
20 days agoHandshake completed628 ms
21 days agoHandshake completed652 ms
22 days agoHandshake completed627 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Prenica(プレニカ) and makes no claim about it beyond what these checks measured.