Remote MCP · Endpoint

セキュリティIoTソリューション MCP server

No. セキュリティIoTソリューション answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
jp.yomitasu/securityiot-theshop-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
218 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
防犯カメラ 監視カメラ ネットワークカメラ どこでもカメラ 住宅・店舗・事務所・駐車場・倉庫・建設現場・農地など…(securityiot.theshop.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of セキュリティIoTソリューション
CheckedResultHandshake
43 minutes agoHandshake completed218 ms
9 days agoHandshake completed279 ms
10 days agoHandshake completed224 ms
11 days agoHandshake completed302 ms
12 days agoHandshake completed220 ms
14 days agoHandshake completed232 ms
15 days agoHandshake completed220 ms
15 days agoHandshake completed234 ms
17 days agoHandshake completed227 ms
19 days agoHandshake completed667 ms
21 days agoHandshake completed653 ms
24 days agoHandshake completed707 ms
26 days agoHandshake completed637 ms

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

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 セキュリティIoTソリューション and makes no claim about it beyond what these checks measured.