blue·auth Document Signing MCP server

Checked 2026-09-07. Alive: no. Handshake: gated.

Category: legal-compliance. API and field schema.

Facts
idricdanyalgil--blueauth
nameblue·auth Document Signing
registry_nameio.github.ricdanyalgil/blueauth-document-signing
repo_urlhttps://github.com/ricdanyalgil/blueauth
endpoint_urlhttps://blueauth.co/api/mcp-server/mcp
transportstreamable-http
aliveno
liveness_reasonunreachable
check_reachableno
check_recent_commitno
check_installablenot verifiable
handshake_statusgated
handshake_checked_at2026-09-07T18:58:28Z
handshake_protocol_versionnot available
handshake_auth_hintBearer realm="blueauth-mcp", resource_metadata="https://blueauth.co/.well-known/oauth-protected-resource/api/mcp-server/mcp", scope="documents signatures certificates stamps custody account"
handshake_auth_discoverableresource_metadata
handshake_failure_layernone
handshake_latency_ms1793
handshake_tools_statenot available
handshake_tool_countnot available
maintenance_statusunknown
last_commit_atnot available
categorylegal-compliance
license_spdxnot available
How to install or connect

Connect your MCP client to https://blueauth.co/api/mcp-server/mcp.

What the checks mean

alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.