Remote MCP · Endpoint
blue·auth Document Signing MCP server
No — it is up, but it requires credentials. blue·auth Document Signing answered 2 hours ago with an authentication challenge rather than a session.
Auth requiredLast checked 2 hours ago
Server URL
https://blueauth.co/api/mcp-server/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- io.github.ricdanyalgil/blueauth-document-signing
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
- Website
- https://blueauth.co/mcp
- Repository
- https://github.com/ricdanyalgil/blueauth
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Credentials required | — |
| 6 hours ago | Credentials required | — |
| 1 day ago | Credentials required | — |
| 2 days ago | Credentials required | — |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 blue·auth Document Signing and makes no claim about it beyond what these checks measured.