Remote MCP · Endpoint

1233.chat MCP server

No. 1233.chat answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://1233.chat/mcp

The last check completed an MCP handshake.

Registry name
chat.1233/marketplace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed292 ms
1 day agoHandshake completed280 ms
3 days agoHandshake completed274 ms
6 days agoHandshake completed289 ms
8 days agoHandshake completed282 ms
9 days agoHandshake completed521 ms
11 days agoHandshake completed276 ms
11 days agoHandshake completed285 ms
13 days agoHandshake completed274 ms
16 days agoHandshake completed316 ms
17 days agoHandshake completed274 ms
19 days agoHandshake completed296 ms
20 days agoHandshake completed298 ms
21 days agoHandshake completed280 ms
22 days agoHandshake completed394 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 1233.chat and makes no claim about it beyond what these checks measured.