Remote MCP · Endpoint

SEO対策研究室 MCP server

No. SEO対策研究室 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
jp.yomitasu/tsuyoshikashiwazaki-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
245 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
SEO コンサルタントの柏崎剛が運営する、検索エンジン対策の情報サイトです。(tsuyoshikashiwazaki.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of SEO対策研究室
CheckedResultHandshake
1 hour agoHandshake completed245 ms
2 days agoHandshake completed275 ms
4 days agoHandshake completed232 ms
6 days agoHandshake completed237 ms
7 days agoHandshake completed616 ms
9 days agoHandshake completed656 ms
10 days agoHandshake completed396 ms
11 days agoHandshake completed221 ms
14 days agoHandshake completed230 ms
15 days agoHandshake completed213 ms
17 days agoHandshake completed206 ms
19 days agoHandshake completed217 ms
20 days agoHandshake completed205 ms
21 days agoHandshake completed204 ms
22 days agoHandshake completed254 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 SEO対策研究室 and makes no claim about it beyond what these checks measured.