Remote MCP · Endpoint

Citation Safe Verifier MCP server

Yes, as of 1 hour ago: the hostname does not resolve.

DownLast checked 1 hour ago

Server URL

https://citationsafe.com/api/mcp

The last check failed: the hostname does not resolve.

Registry name
com.citationsafe/verifier
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
31.6% from 19 checks
Described by its publisher as
Verifies legal citations vs primary sources: existence, quote match, proposition support.
Repository
https://github.com/andrewjgaber-commits/empire-distribution
Listing
From the official MCP registry (active).
Recent checks of Citation Safe Verifier
CheckedResultHandshake
1 hour agoFailed - the hostname does not resolve—
19 hours agoFailed - the hostname does not resolve—
2 days agoFailed - the hostname does not resolve—
3 days agoFailed - the hostname does not resolve—
4 days agoFailed - the hostname does not resolve—
5 days agoFailed - the hostname does not resolve—
6 days agoFailed - the hostname does not resolve—
8 days agoFailed - the hostname does not resolve—
10 days agoFailed - the hostname does not resolve—
13 days agoFailed - the hostname does not resolve—
15 days agoFailed - the hostname does not resolve—
17 days agoFailed - the hostname does not resolve—
19 days agoFailed - the server returned an HTTP error—
21 days agoHandshake completed100 ms
23 days agoHandshake completed278 ms
25 days agoHandshake completed176 ms
27 days agoHandshake completed107 ms
28 days agoHandshake completed260 ms
29 days agoHandshake completed133 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Citation Safe Verifier and makes no claim about it beyond what these checks measured.