Remote MCP · Endpoint

Evercraft Machine Commerce MCP server

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

DownLast checked 1 hour ago

Server URL

https://evercraft-ai-suite-08c4d2b8.base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/machineCommerceMcp

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

Registry name
io.github.jgaethle10/evercraft-machine-commerce
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
34 tools
Uptime, last 30 days
36.8% from 19 checks
Described by its publisher as
Start with match_offer to route a user problem to the smallest public-safe Evercraft capability.
Website
https://evercraft-ai-suite-08c4d2b8.base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/machineCommerceGateway?view=docs
Repository
https://github.com/jgaethle10/forge-operator
Listing
From the official MCP registry (active).
Recent checks of Evercraft Machine Commerce
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed577 ms
22 days agoHandshake completed225 ms
24 days agoHandshake completed583 ms
26 days agoHandshake completed442 ms
27 days agoHandshake completed528 ms
29 days agoHandshake completed443 ms
29 days agoHandshake completed688 ms

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

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 Evercraft Machine Commerce and makes no claim about it beyond what these checks measured.