Remote MCP · Endpoint

BotClaw · Agent Observer MCP server

No. BotClaw · Agent Observer answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://botclaw.tech/api/mcp

The last check completed an MCP handshake.

Registry name
tech.botclaw/agent-observer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
547 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only agent radar, weekly editions, sourced guides, scenario choices and revision sync.
Listing
From the official MCP registry (active).
Recent checks of BotClaw · Agent Observer
CheckedResultHandshake
7 hours agoHandshake completed547 ms
3 days agoHandshake completed307 ms
12 days agoHandshake completed328 ms
12 days agoHandshake completed233 ms
14 days agoHandshake completed216 ms
15 days agoHandshake completed63 ms
16 days agoHandshake completed334 ms
17 days agoHandshake completed235 ms
18 days agoHandshake completed332 ms
20 days agoHandshake completed665 ms
22 days agoHandshake completed203 ms
25 days agoHandshake completed408 ms
27 days agoHandshake completed90 ms
29 days agoHandshake completed221 ms

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

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 BotClaw · Agent Observer and makes no claim about it beyond what these checks measured.