Remote MCP · Endpoint

iter0 MCP server

No. iter0 answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://iter0.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.inchwormz/iter0-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Build and edit launch-ready websites for tech founders from a brief or an authorised reference.
Listing
From the official MCP registry (active).
Recent checks of iter0
CheckedResultHandshake
34 minutes agoHandshake completed132 ms
3 days agoHandshake completed107 ms
13 days agoHandshake completed97 ms
13 days agoHandshake completed3.17 s
15 days agoHandshake completed169 ms
16 days agoHandshake completed173 ms
17 days agoHandshake completed158 ms
18 days agoHandshake completed146 ms
18 days agoHandshake completed118 ms
20 days agoHandshake completed157 ms
22 days agoHandshake completed142 ms
25 days agoHandshake completed101 ms

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

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