Is InfoLang Memory down?

MCP serverBy infolang.ai. How to connect and its trust score are on the listing page.

Down

Yes, InfoLang Memory is down.

It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 530.

Latest check

Last check: 30 h ago (26 Oct 2026, 15:49 UTC)
Response time: Not measured
Next check: In about 46 h
How often: About every 3 days over the last 7 days

Uptime

Last 24 hours-0 checks

Last 7 days0.0%2 checks

Last 30 days0.0%12 checks

All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 3 days 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

When	Result	HTTP	Time
26 Oct 2026, 15:49 UTC	initialize returned HTTP 530	530	170 ms
23 Oct 2026, 11:28 UTC	initialize returned HTTP 530	530	232 ms
20 Oct 2026, 08:26 UTC	initialize returned HTTP 530	530	679 ms
19 Oct 2026, 07:10 UTC	initialize returned HTTP 530	530	334 ms
18 Oct 2026, 03:26 UTC	initialize returned HTTP 530	530	253 ms
16 Oct 2026, 23:42 UTC	initialize returned HTTP 530	530	242 ms
15 Oct 2026, 18:58 UTC	initialize returned HTTP 530	530	579 ms
14 Oct 2026, 13:23 UTC	initialize returned HTTP 530	530	384 ms
13 Oct 2026, 11:17 UTC	initialize returned HTTP 530	530	297 ms
12 Oct 2026, 09:23 UTC	initialize returned HTTP 530	530	697 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 3 days 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.