Remote MCP · Endpoint

Smolabot MCP server

No. Smolabot answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://smolabot.arison8.com/mcp

The last check completed an MCP handshake.

Registry name
com.arison8/smolabot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
113 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Deterministic decision guardrail for AI agents and bots. Verifies pre-trade economics (long-only).
Listing
From the official MCP registry (active).
Recent checks of Smolabot
CheckedResultHandshake
48 minutes agoHandshake completed113 ms
10 days agoHandshake completed120 ms
10 days agoHandshake completed149 ms
11 days agoHandshake completed259 ms
12 days agoHandshake completed70 ms
14 days agoHandshake completed340 ms
14 days agoHandshake completed86 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed75 ms
19 days agoHandshake completed53 ms
21 days agoHandshake completed377 ms
24 days agoHandshake completed397 ms
26 days agoHandshake completed108 ms
28 days agoHandshake completed127 ms

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

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