Remote MCP · Endpoint

VISEON Ask MCP server

No. VISEON Ask answered an MCP handshake 19 hours ago.

UpLast checked 19 hours ago

Server URL

https://viseon.io/mcp

The last check completed an MCP handshake.

Registry name
io.viseon/semantic-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
536 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
VISEON's Schema.org knowledge graph: products, services, people, FAQs and terms, from viseon.io
Listing
From the official MCP registry (active).
Recent checks of VISEON Ask
CheckedResultHandshake
19 hours agoHandshake completed536 ms
2 days agoHandshake completed410 ms
4 days agoHandshake completed372 ms
7 days agoHandshake completed324 ms
9 days agoHandshake completed315 ms
10 days agoHandshake completed652 ms
12 days agoHandshake completed831 ms
13 days agoHandshake completed549 ms
14 days agoHandshake completed650 ms
17 days agoHandshake completed410 ms
18 days agoHandshake completed395 ms
20 days agoHandshake completed415 ms
21 days agoHandshake completed385 ms
22 days agoHandshake completed450 ms

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

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