Remote MCP · Endpoint

com.seoapi/coccocbot MCP server

No. com.seoapi/coccocbot answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://coccocbot.seoapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.seoapi/coccocbot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
75 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Validate Cốc Cốc Bot IP addresses. Remote MCP validate_ip tool.
Website
https://seoapi.com/coccocbot/
Listing
From the official MCP registry (active).
Recent checks of com.seoapi/coccocbot
CheckedResultHandshake
2 hours agoHandshake completed75 ms
1 day agoHandshake completed47 ms
2 days agoHandshake completed84 ms
3 days agoHandshake completed112 ms
4 days agoHandshake completed152 ms
5 days agoHandshake completed43 ms
7 days agoHandshake completed82 ms
9 days agoHandshake completed99 ms
12 days agoHandshake completed170 ms
14 days agoHandshake completed449 ms
16 days agoHandshake completed69 ms
18 days agoHandshake completed32 ms
20 days agoHandshake completed68 ms
22 days agoHandshake completed45 ms
24 days agoHandshake completed25 ms
26 days agoHandshake completed84 ms
27 days agoHandshake completed66 ms
29 days agoHandshake completed270 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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