Remote MCP · Endpoint

Sigil MCP server

No. Sigil answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://sigilbrandstudio.com/mcp

The last check completed an MCP handshake.

Registry name
com.auto-units/sigil
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
2 tools
Uptime, last 30 days
61.5% from 13 checks
Described by its publisher as
Brand reviews from a public website and an optional product document.
Listing
From the official MCP registry (active).
Recent checks of Sigil
CheckedResultHandshake
6 days agoHandshake completed77 ms
7 days agoHandshake completed129 ms
7 days agoHandshake completed139 ms
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed181 ms
17 days agoHandshake completed141 ms
20 days agoHandshake completed252 ms
22 days agoHandshake completed106 ms
24 days agoHandshake completed122 ms

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

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