Remote MCP · Endpoint

jp.afdb/mcp MCP server

No. jp.afdb/mcp answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://mcp.afdb.jp/mcp

The last check completed an MCP handshake.

Registry name
jp.afdb/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search current Japanese point-site rewards, conditions, yen values, and observation times.
Listing
From the official MCP registry (active).
Recent checks of jp.afdb/mcp
CheckedResultHandshake
35 minutes agoHandshake completed142 ms
9 days agoHandshake completed168 ms
10 days agoHandshake completed315 ms
11 days agoHandshake completed262 ms
12 days agoHandshake completed207 ms
14 days agoHandshake completed174 ms
14 days agoHandshake completed189 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed196 ms
19 days agoHandshake completed275 ms
21 days agoHandshake completed142 ms
24 days agoHandshake completed250 ms
26 days agoHandshake completed165 ms
28 days agoHandshake completed133 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with jp.afdb/mcp and makes no claim about it beyond what these checks measured.