Remote MCP · Endpoint

Japan Organic JAS Certified Operators MCP server

No. Japan Organic JAS Certified Operators answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://jp-organic-jas-production.mk-career-planning.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.mk-career-planning/jp-organic-jas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.20 s
Tools exposed
4 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Is this operator in Japan's organic JAS certified list? Hosted; tracks list changes. Relay only.
Listing
From the official MCP registry (active).
Recent checks of Japan Organic JAS Certified Operators
CheckedResultHandshake
1 hour agoHandshake completed1.20 s
2 days agoHandshake completed879 ms
4 days agoHandshake completed710 ms

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

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 Japan Organic JAS Certified Operators and makes no claim about it beyond what these checks measured.