Remote MCP · Endpoint

io.dozier/exposure-audit MCP server

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

DownLast checked 1 hour ago

Server URL

https://dozier.io/backend/mcp

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

Registry name
io.dozier/exposure-audit
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
70.6% from 17 checks
Described by its publisher as
Free AI-visibility and competitive Exposure Audit for any domain. No account, no API key.
Listing
From the official MCP registry (active).
Recent checks of io.dozier/exposure-audit
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoHandshake completed44 ms
9 days agoHandshake completed46 ms
12 days agoHandshake completed72 ms
13 days agoHandshake completed92 ms
15 days agoHandshake completed88 ms
16 days agoHandshake completed73 ms
18 days agoHandshake completed65 ms
19 days agoHandshake completed44 ms
20 days agoHandshake completed64 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed75 ms
22 days agoHandshake completed97 ms

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

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 io.dozier/exposure-audit and makes no claim about it beyond what these checks measured.