Is SCRIPTMASTERLABS — SML agent-safety down?

MCP serverBy sml-agent-safety.onrender.com. How to connect and its trust score are on the listing page.

Down

Yes, SCRIPTMASTERLABS — SML agent-safety is down.

It has failed every check since 6 Nov 2026, 05:34 UTC (4 days 9 h, 5 checks). Latest error: initialize returned HTTP 503. It last passed on 5 Nov 2026, 14:45 UTC.

Latest check

Last check
20 h ago (9 Nov 2026, 17:52 UTC)
Response time
Not measured (typical 261 ms)
Next check
In about 2 h
How often
About every 14 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days44.4%9 checks
Last 30 days44.4%9 checks
All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 14 hours over the last 7 days.

Outages in the last 30 days

1 outage, 4 days 9 h of failed checks in total.

StartedDurationFailed checksFirst error
6 Nov 2026, 05:34 UTCOngoing, 4 days 9 h so far5initialize returned HTTP 503

Times are when our checks ran, about every 14 hours for this listing, so start times and durations are accurate to about that.

Recent checks

WhenResultHTTPTime
9 Nov 2026, 17:52 UTCinitialize returned HTTP 503503212 ms
8 Nov 2026, 10:53 UTCinitialize returned HTTP 503503699 ms
7 Nov 2026, 04:01 UTCinitialize returned HTTP 503503213 ms
6 Nov 2026, 16:47 UTCinitialize returned HTTP 503503691 ms
6 Nov 2026, 05:34 UTCinitialize returned HTTP 503503240 ms
5 Nov 2026, 14:45 UTCPassed200259 ms
5 Nov 2026, 00:06 UTCPassed200596 ms
4 Nov 2026, 09:54 UTCPassed200715 ms
3 Nov 2026, 19:35 UTCPassed200261 ms

How we check

Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.

Checks come from our server, about every 14 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.

If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.