Remote MCP · Endpoint

Holston AI MCP server

Yes, as of 6 days ago: the server returned an HTTP error.

DownLast checked 6 days ago

Server URL

https://holstonai.com/mcp

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

Registry name
com.holstonai/holston-ai
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
12 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
AI visibility audits, llms.txt and schema generators, instant quotes, missed-call and ROI tools.
Listing
From the official MCP registry (active).
Recent checks of Holston AI
CheckedResultHandshake
6 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed167 ms
7 days agoHandshake completed179 ms
9 days agoHandshake completed149 ms
10 days agoHandshake completed149 ms
11 days agoHandshake completed172 ms
12 days agoHandshake completed189 ms
13 days agoHandshake completed207 ms
15 days agoHandshake completed501 ms
17 days agoHandshake completed139 ms
20 days agoHandshake completed205 ms
22 days agoHandshake completed166 ms
24 days agoHandshake completed170 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 Holston AI and makes no claim about it beyond what these checks measured.