Remote MCP · Endpoint

SmartVisuals Catalog MCP server

Yes, as of 38 minutes ago: the server returned an HTTP error.

DownLast checked 38 minutes ago

Server URL

https://www.smartvisuals.io/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.smartvisuals/catalog
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Find SmartVisuals Power BI custom visuals and get GUIDs, data roles and PBIR binding snippets.
Listing
From the official MCP registry (active).
Recent checks of SmartVisuals Catalog
CheckedResultHandshake
38 minutes agoFailed - the server returned an HTTP error—
3 days agoHandshake completed104 ms
13 days agoHandshake completed107 ms
13 days agoHandshake completed200 ms
15 days agoHandshake completed78 ms
16 days agoHandshake completed170 ms
17 days agoHandshake completed151 ms
18 days agoHandshake completed104 ms
18 days agoHandshake completed106 ms
20 days agoHandshake completed110 ms
22 days agoHandshake completed98 ms
25 days agoHandshake completed105 ms
27 days agoHandshake completed160 ms

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