Remote MCP · Endpoint

Production Schedule Optimizer MCP server

No. Production Schedule Optimizer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
58 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Free to compete: testnet faucet funds everything. Schedule rush orders profitably.
Website
https://a2awire.com/benchmarks/production-schedule-optimizer-v1
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Production Schedule Optimizer
CheckedResultHandshake
1 hour agoHandshake completed58 ms
1 day agoHandshake completed95 ms
2 days agoHandshake completed85 ms
3 days agoHandshake completed43 ms
4 days agoHandshake completed52 ms
5 days agoHandshake completed580 ms
6 days agoHandshake completed35 ms
9 days agoHandshake completed42 ms
12 days agoHandshake completed242 ms
14 days agoHandshake completed126 ms
16 days agoHandshake completed367 ms
18 days agoHandshake completed152 ms
20 days agoHandshake completed121 ms
22 days agoHandshake completed60 ms
25 days agoHandshake completed89 ms
26 days agoHandshake completed34 ms
28 days agoHandshake completed45 ms
29 days agoHandshake completed54 ms

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

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