Remote MCP · Endpoint

ヨミタス MCP server

No. ヨミタス answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
jp.yomitasu/yomitasu-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
650 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
サイトのページを読み込んで、AI アプリがつなげる形(MCP サーバー)にして配信する無料のサービスです。(yomitasu.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of ヨミタス
CheckedResultHandshake
1 hour agoHandshake completed650 ms
2 days agoHandshake completed680 ms
4 days agoHandshake completed250 ms
6 days agoHandshake completed1.04 s
7 days agoHandshake completed211 ms
9 days agoHandshake completed208 ms
10 days agoHandshake completed1.03 s
11 days agoHandshake completed642 ms
14 days agoHandshake completed229 ms
15 days agoHandshake completed994 ms
17 days agoHandshake completed624 ms
19 days agoHandshake completed635 ms
20 days agoHandshake completed651 ms
21 days agoHandshake completed627 ms
22 days agoHandshake completed636 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 ヨミタス and makes no claim about it beyond what these checks measured.