Remote MCP · Endpoint

DocuQueue MCP MCP server

No. DocuQueue MCP answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://docuqueue.com/mcp/v1

The last check completed an MCP handshake.

Registry name
io.github.dvcoolarun/docuqueue-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
121 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MCP server for PDF generation, form filling, batch invoices and contracts. MIT, free tier, hosted.
Listing
From the official MCP registry (active).
Recent checks of DocuQueue MCP
CheckedResultHandshake
13 minutes agoHandshake completed121 ms
10 days agoHandshake completed108 ms
10 days agoHandshake completed101 ms
11 days agoHandshake completed106 ms
13 days agoHandshake completed109 ms
14 days agoHandshake completed96 ms
14 days agoHandshake completed99 ms
15 days agoHandshake completed176 ms
17 days agoHandshake completed118 ms
19 days agoHandshake completed90 ms
21 days agoHandshake completed114 ms
24 days agoHandshake completed95 ms
26 days agoHandshake completed123 ms
28 days agoHandshake completed111 ms

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

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 DocuQueue MCP and makes no claim about it beyond what these checks measured.