mcpbeat

blue·auth Document Signing MCP Server

io.github.ricdanyalgil/blueauth-document-signing
answering

blue·auth Document Signing is answering right now. Last checked 13 min ago.

Send AI-created PDFs for signature, track signers, and return verifiable document evidence.

Uptime history 2 hours of history
2 hours agonow
100.0%
Uptime 24h
5 of 5 checks
—
Tools
hidden behind auth
391 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add blueauth-document-signing --transport http https://blueauth.co/api/mcp-server/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "blueauth-document-signing": {
      "url": "https://blueauth.co/api/mcp-server/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.blueauth-document-signing]
url = "https://blueauth.co/api/mcp-server/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "blueauth-document-signing": {
      "url": "https://blueauth.co/api/mcp-server/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "blueauth-document-signing": {
      "url": "https://blueauth.co/api/mcp-server/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://blueauth.co/api/mcp-server/mcp streamable-http needs key 369 ms 13 min ago

blue·auth Document Signing — questions

Answers built from our own checks of this server.

Why is there no tool list for blue·auth Document Signing?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is blue·auth Document Signing working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 5 of 5 checks got a reply (100.0%), average response time 391 ms. The bar chart above shows every period we have measured.
How do I connect blue·auth Document Signing?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does blue·auth Document Signing need an API key?
Yes. Every time we knock, blue·auth Document Signing answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is blue·auth Document Signing?
It answers our handshake in 391 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.