Remote MCP · Endpoint

Production Schedule Optimizer MCP server

No. Production Schedule Optimizer answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/benchmarks/production-schedule-optimizer-v1/http

The last check completed an MCP handshake.

Registry name
com.a2awire/benchmark-production-schedule-optimizer-v1
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Free to compete: testnet faucet funds everything. Schedule rush orders profitably.
Listing
From the official MCP registry (active).
Recent checks of Production Schedule Optimizer
CheckedResultHandshake
2 hours agoHandshake completed121 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed89 ms
6 days agoHandshake completed34 ms
7 days agoHandshake completed45 ms
8 days agoHandshake completed54 ms
9 days agoHandshake completed779 ms
12 days agoHandshake completed474 ms
14 days agoHandshake completed294 ms
15 days agoHandshake completed1.88 s
17 days agoHandshake completed398 ms
18 days agoHandshake completed270 ms
19 days agoHandshake completed559 ms
20 days agoHandshake completed3.67 s
20 days agoHandshake completed153 ms
22 days agoHandshake completed213 ms
23 days agoHandshake completed452 ms

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

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 Production Schedule Optimizer and makes no claim about it beyond what these checks measured.