io.github.ptyagiegnyte/egnyte-remote MCP server

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

Category: file-storage. API and field schema.

Facts
idsachin-shetty--egnyte-ai-samples
nameio.github.ptyagiegnyte/egnyte-remote
registry_nameio.github.ptyagiegnyte/egnyte-remote
repo_urlhttps://github.com/sachin-shetty/egnyte-ai-samples
endpoint_urlhttps://ptyagiegnyte.github.io/egnyte-remote/mcp
transportstreamable-http
aliveno
liveness_reasonunreachable
check_reachableno
check_recent_commitno
check_installablenot verifiable
handshake_statusunknown
handshake_checked_at2026-09-07T18:58:41Z
handshake_protocol_versionnot available
handshake_auth_hinthttp:405
handshake_auth_discoverablenot available
handshake_failure_layerhttp
handshake_latency_ms486
handshake_tools_statenot available
handshake_tool_countnot available
maintenance_statusunknown
last_commit_atnot available
categoryfile-storage
license_spdxnot available
How to install or connect

Connect your MCP client to https://ptyagiegnyte.github.io/egnyte-remote/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.