Remote MCP · Endpoint

Aplos Automation Budget MCP server

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

DownLast checked 5 days ago

Server URL

https://aplosai.netlify.app/.netlify/functions/automation-budget-mcp

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

Registry name
com.aplosai/automation-budget
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
46.7% from 15 checks
Described by its publisher as
Estimate automation cash costs, time-valued capacity and simple payback from your assumptions.
Listing
From the official MCP registry (active).
Recent checks of Aplos Automation Budget
CheckedResultHandshake
5 days agoFailed - the server returned an HTTP error—
6 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—
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—
12 days agoFailed - the server returned an HTTP error—
14 days agoHandshake completed207 ms
17 days agoHandshake completed333 ms
19 days agoHandshake completed402 ms
21 days agoHandshake completed216 ms
24 days agoHandshake completed527 ms
25 days agoHandshake completed378 ms
28 days agoHandshake completed212 ms

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

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