Remote MCP · Endpoint

GoAI Moat Cross-Border Inventory & Fulfillment MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://inventory.mcp.goaimoat.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.goaimoat/inventory-fulfillment
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
52.9% from 17 checks
Described by its publisher as
Safety-stock & reorder planning, FBA-vs-FBM decision, and inventory health audit for sellers
Website
https://goaimoat.com/
Repository
https://github.com/jayniebingyu-cyber/goaimoat-ai-visibility-mcp
Listing
From the official MCP registry (active).
Recent checks of GoAI Moat Cross-Border Inventory & Fulfillment
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
14 days agoHandshake completed640 ms
15 days agoHandshake completed634 ms
17 days agoHandshake completed630 ms
19 days agoHandshake completed631 ms
20 days agoHandshake completed635 ms
21 days agoHandshake completed638 ms
22 days agoHandshake completed637 ms
22 days agoHandshake completed636 ms
23 days agoHandshake completed638 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 9 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.

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 GoAI Moat Cross-Border Inventory & Fulfillment and makes no claim about it beyond what these checks measured.