Remote MCP · Endpoint

Esprit Delasse MCP server

No. Esprit Delasse answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.yomitasu.jp/s/esprit-delasse-com/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/esprit-delasse-com
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
218 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
良質なスピリチュアルニュースをお届けするEsprit Delasse(エスプリ・デラッセ)。(esprit-delasse.com の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of Esprit Delasse
CheckedResultHandshake
1 hour agoHandshake completed218 ms
1 day agoHandshake completed218 ms
2 days agoHandshake completed227 ms
2 days agoHandshake completed213 ms
4 days agoHandshake completed226 ms
6 days agoHandshake completed239 ms
9 days agoHandshake completed225 ms
11 days agoHandshake completed261 ms
13 days agoHandshake completed230 ms
16 days agoHandshake completed225 ms
18 days agoHandshake completed240 ms
20 days agoHandshake completed226 ms
22 days agoHandshake completed664 ms
23 days agoHandshake completed713 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 Esprit Delasse and makes no claim about it beyond what these checks measured.