Remote MCP · Endpoint

1233.chat MCP server

Yes, as of 2 days ago: the TLS certificate could not be verified.

DownLast checked 2 days ago

Server URL

https://1233.chat/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
chat.1233/marketplace
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
88.2% from 17 checks
Described by its publisher as
Search goods and services listings on 1233.chat, a classifieds board in Bishkek, Kyrgyzstan.
Listing
From the official MCP registry (active).
Recent checks of 1233.chat
CheckedResultHandshake
2 days agoFailed - the TLS certificate could not be verified—
3 days agoFailed - the connection was refused or dropped—
3 days agoHandshake completed282 ms
5 days agoHandshake completed434 ms
6 days agoHandshake completed374 ms
7 days agoHandshake completed300 ms
8 days agoHandshake completed737 ms
9 days agoHandshake completed286 ms
11 days agoHandshake completed284 ms
13 days agoHandshake completed280 ms
16 days agoHandshake completed286 ms
18 days agoHandshake completed290 ms
20 days agoHandshake completed292 ms
22 days agoHandshake completed280 ms
24 days agoHandshake completed274 ms
26 days agoHandshake completed289 ms
28 days agoHandshake completed282 ms
30 days agoHandshake completed521 ms
31 days agoHandshake completed276 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 25 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.

Listing data comes from the official MCP registry. Glide is not affiliated with 1233.chat and makes no claim about it beyond what these checks measured.