Remote MCP · Endpoint

agent-lint MCP server

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

DownLast checked 41 minutes ago

Server URL

https://runningunattended.com/api/mcp

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

Registry name
com.runningunattended/agent-lint
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Checks CLAUDE.md, AGENTS.md or a system prompt for 12 safeguards unattended agents need.
Listing
From the official MCP registry (active).
Recent checks of agent-lint
CheckedResultHandshake
41 minutes agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed142 ms
9 days agoHandshake completed145 ms
11 days agoHandshake completed132 ms
13 days agoHandshake completed197 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed87 ms
19 days agoHandshake completed104 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed173 ms
23 days agoHandshake completed682 ms

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