Remote MCP · Endpoint
SEO対策研究室 MCP MCP server
No. SEO対策研究室 MCP answered an MCP handshake 4 hours ago.
UpLast checked 4 hours ago
Server URL
https://mcp.tsuyoshikashiwazaki.jp/
The last check completed an MCP handshake.
- Registry name
- jp.tsuyoshikashiwazaki/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 715 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- SEO対策研究室（柏崎剛）の公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 hours ago | Handshake completed | 715 ms |
| 15 hours ago | Handshake completed | 597 ms |
| 1 day ago | Handshake completed | 597 ms |
| 2 days ago | Handshake completed | 599 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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対策研究室 MCP and makes no claim about it beyond what these checks measured.