Remote MCP · Endpoint

SOVIQ AI MCP server

Yes, as of 1 day ago: the server returned an HTTP error.

DownLast checked 1 day ago

Server URL

https://app.soviqai.com/mcp

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

Registry name
com.soviqai/soviq
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
2 checks from 2 checks
Described by its publisher as
Construction billing: pay apps, schedule of values, change orders, receivables, cash forecast.
Listing
From the official MCP registry (active).
Recent checks of SOVIQ AI
CheckedResultHandshake
1 day agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—

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

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