Remote MCP · Endpoint

Evercraft Clip MCP server

Yes, as of 2 days ago: the server returned an HTTP error.

DownLast checked 2 days ago

Server URL

https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp

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

Registry name
io.github.jgaethle10/evercraft-clip
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
23.5% from 17 checks
Described by its publisher as
Start with plan_clip_job to plan authorized social-video work and route complex media when needed.
Website
https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipAgentGateway?view=docs
Repository
https://github.com/jgaethle10/forge-operator
Listing
From the official MCP registry (active).
Recent checks of Evercraft Clip
CheckedResultHandshake
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 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—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed257 ms
25 days agoHandshake completed423 ms
27 days agoHandshake completed395 ms
29 days agoHandshake completed2.76 s
30 days agoHandshake completed1.14 s
32 days agoHandshake completed462 ms

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

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