Remote MCP · Endpoint

Unseen Workflow Compiler MCP server

No. Unseen Workflow Compiler answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://unseendocs.in/mcp

The last check completed an MCP handshake.

Registry name
io.github.eyeinthesky6/unseen-workflow-compiler
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.24 s
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Compile SOPs, policies, and playbooks into source-grounded visual flowcharts (SVG, Mermaid, JSON).
Listing
From the official MCP registry (active).
Recent checks of Unseen Workflow Compiler
CheckedResultHandshake
3 hours agoHandshake completed1.24 s
3 days agoHandshake completed572 ms
13 days agoHandshake completed634 ms
14 days agoHandshake completed613 ms
15 days agoHandshake completed545 ms
16 days agoHandshake completed701 ms
18 days agoHandshake completed490 ms
18 days agoHandshake completed558 ms
19 days agoHandshake completed583 ms
21 days agoHandshake completed725 ms
22 days agoHandshake completed723 ms
25 days agoHandshake completed530 ms
27 days agoHandshake completed577 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Unseen Workflow Compiler and makes no claim about it beyond what these checks measured.