Remote MCP · Endpoint

Is Agentic MCP server

No. Is Agentic answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fk2efxqdersj346fbaw43tpqwi0qmist.lambda-url.us-west-2.on.aws/mcp

The last check completed an MCP handshake.

Registry name
io.github.clo-paz/is-agentic-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
286 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Shop the Is Agentic store with read-only catalog discovery, gift recommendations and cart links.
Listing
From the official MCP registry (active).
Recent checks of Is Agentic
CheckedResultHandshake
1 hour agoHandshake completed286 ms
9 days agoHandshake completed514 ms
10 days agoHandshake completed276 ms
11 days agoHandshake completed230 ms
12 days agoHandshake completed231 ms
14 days agoHandshake completed220 ms
14 days agoHandshake completed271 ms
15 days agoHandshake completed246 ms
17 days agoHandshake completed233 ms
19 days agoHandshake completed218 ms
21 days agoHandshake completed247 ms
24 days agoHandshake completed254 ms
26 days agoHandshake completed549 ms
28 days agoHandshake completed221 ms

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

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