Remote MCP · Endpoint

株式会社一創 コーポレートサイト MCP server

No. 株式会社一創 コーポレートサイト answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://www.issoh.co.jp/mcp

The last check completed an MCP handshake.

Registry name
jp.co.issoh/corporate-site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
株式会社一創(issoh.co.jp)の技術記事・サービス・制作実績を検索できる MCP サーバー。システム開発・AI・クラウド・Web 制作の日本語情報
Listing
From the official MCP registry (active).
Recent checks of 株式会社一創 コーポレートサイト
CheckedResultHandshake
1 day agoHandshake completed52 ms
3 days agoHandshake completed78 ms
5 days agoHandshake completed88 ms
7 days agoHandshake completed85 ms
8 days agoHandshake completed86 ms
9 days agoHandshake completed69 ms
12 days agoHandshake completed55 ms
13 days agoHandshake completed81 ms
15 days agoHandshake completed73 ms
16 days agoHandshake completed72 ms
17 days agoHandshake completed31 ms
19 days agoHandshake completed55 ms
20 days agoHandshake completed69 ms
20 days agoHandshake completed70 ms
21 days agoHandshake completed74 ms
22 days agoHandshake completed61 ms

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

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.