yaver-cli

MCPcommunity
v1.99.411io.github.yaver-ioUnknownUpdated 6d agonpmGitHub

Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6d agoLast update
Package
Authorio.github.yaver-io
LicenseUnknown
Version1.99.411
Sourcenpm+mcp-registry
npmyaver-cli
GitHubkivanccakmak/yaver.io
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies11 resolved · 1 with advisories
Tool surface—
Security scan⚠ Warnings (2)v1.99.263 · 2mo ago
HIGH@modelcontextprotocol/sdk@0.6.1Anthropic's MCP TypeScript SDK has a ReDoS vulnerability · transitiveHIGH@modelcontextprotocol/sdk@0.6.1Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default · transitive
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.

Keywords
mcp