Is Backtest Cost Sensitivity down?

MCP serverBy backtest-cost-sensitivity-mcp.mcpize.run. How to connect and its trust score are on the listing page.

Up

No, Backtest Cost Sensitivity is up.

It passed its latest check 6 h ago in 763 ms, and every check since we started checking it on 11 Oct 2026.

Latest check

Last check
6 h ago (19 Oct 2026, 14:11 UTC)
Response time
763 ms (typical 622 ms)
Next check
In about 4 h
How often
About every 10 hours over the last 7 days

Uptime

Last 24 hours100%3 checks
Last 7 days100%17 checks
Last 30 days100%20 checks
All checks passedSome failedAll failedNot checked

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

Outages in the last 30 days

No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.

Recent checks

WhenResultHTTPTime
19 Oct 2026, 14:11 UTCPassed401763 ms
19 Oct 2026, 05:14 UTCPassed401527 ms
18 Oct 2026, 20:31 UTCPassed401809 ms
18 Oct 2026, 10:03 UTCPassed401630 ms
17 Oct 2026, 23:09 UTCPassed401596 ms
17 Oct 2026, 12:28 UTCPassed401803 ms
17 Oct 2026, 01:34 UTCPassed401778 ms
16 Oct 2026, 15:50 UTCPassed401692 ms
16 Oct 2026, 05:20 UTCPassed401607 ms
15 Oct 2026, 19:36 UTCPassed401750 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 10 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.