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/seo-contencial-co-jp/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/seo-contencial-co-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
631 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
SEO 対策とサイト改善を手がける株式会社コンテンシャルの公式サイトです。(seo.contencial.co.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of 株式会社コンテンシャル
CheckedResultHandshake
1 hour agoHandshake completed631 ms
2 days agoHandshake completed662 ms
4 days agoHandshake completed9.21 s
6 days agoHandshake completed8.84 s
8 days agoHandshake completed620 ms
10 days agoHandshake completed600 ms
12 days agoHandshake completed652 ms
13 days agoHandshake completed1.08 s
15 days agoHandshake completed772 ms
16 days agoHandshake completed666 ms
18 days agoHandshake completed624 ms
20 days agoHandshake completed618 ms
21 days agoHandshake completed721 ms
23 days agoHandshake completed671 ms

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

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.