Publisher portfolio

yaver-io

io.github.yaver-io Verified namespace

Explore the MCP servers published by yaver-io, with independent connection checks, performance measurements, and setup instructions for each project.

Active projects in this portfolio. Deleted and deprecated registry rows are excluded.

Active servers with a recorded connection probe

Latest stored probe connected. This is not a live guarantee.

Distinct source repositories linked by the active listings

Portfolio overview

MCP servers

Compare connection status and measurements. Open a server for its tools, check results, and client configuration.

Dated server measurements. The status describes the last probe or a listed authentication requirement. Checks that have not been measured are not failures. Open a server to inspect the evidence.
Server / capability	Last probe	Median latency	Checks passed	Last checked
Yaver yaver-io Phone-first OpenCode MCP for trusted devices: run, build, deploy, and manage endpoint-local tools. Developer Tools Code & DevOps	Not measured	Not measured	4 / 6	Not checked yet

Company & identity

yaver-io publishes MCP servers under the io.github.yaver-io namespace. This namespace is associated with a GitHub login in the MCP Registry.

Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.