Remote MCP · Endpoint

@エール | Aile Jobs MCP server

No. @エール | Aile Jobs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.aile-ai.jp/api/public/mcp

The last check completed an MCP handshake.

Registry name
jp.aile-ai/aile-jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
526 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
日本の掲載中・公開正社員求人の検索、求人詳細、職種別年収相場を提供する読み取り専用MCPサーバー
Listing
From the official MCP registry (active).
Recent checks of @エール | Aile Jobs
CheckedResultHandshake
1 hour agoHandshake completed526 ms
3 days agoHandshake completed505 ms
13 days agoHandshake completed508 ms
14 days agoHandshake completed533 ms
15 days agoHandshake completed480 ms
16 days agoHandshake completed504 ms
18 days agoHandshake completed460 ms
18 days agoHandshake completed463 ms
19 days agoHandshake completed458 ms
21 days agoHandshake completed460 ms
22 days agoHandshake completed462 ms
25 days agoHandshake completed464 ms
27 days agoHandshake completed456 ms
30 days agoHandshake completed508 ms

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

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 @エール | Aile Jobs and makes no claim about it beyond what these checks measured.