Record source
Official MCP registryThe named source does not confirm ownership or quality.
Open source dataAgent infrastructure
Yaver
Technical interface from yaver.io. Check the source for its exact purpose.
Named provider: yaver.io
Technical Score
Not enough data to calculateCoverage 0% · technical-v2
User Rating
There are no published reviews yetPublished reviews are not mixed with technical observations.
Go to reviewsLatest endpoint observation
There is no endpoint observation yetThe status applies only to the checked endpoint, not the whole service.
Open historyAbout this service
What it does
Technical interface from yaver.io. Check the source for its exact purpose.
Task category
Agent infrastructure
Named provider
yaver.io
How to connect
MCP
Protocols: mcp
User reviews
There are no published reviews yet
New reviews are not being accepted yet.
Technical observation history
Recent endpoint checks
No check history has been published yet.
Problems in the observation history
There are no problems in the available history.
Endpoints and technical capabilities
Each observation applies to a specific endpoint.
The record has no endpoint available for technical checking.
- Access methods
- MCP
- Protocols
mcp- Version
1.99.406- Technical record name
Yaver
Source data
This data comes from the named source. It is not proof of ownership or an independent quality assessment.
Original description
Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.
Open the named source recordOpens in a new tab- Record source
- Official MCP registry
- Source updated
- 9 Aug 2026, 08:38 UTC
- Ownership status
- Owner not confirmed
- Source identifier
mcp_registry- Repository
https://github.com/kivanccakmak/yaver.ioOpens in a new tab
Corrections and future affiliation verification
A public record can be corrected through support without hiding its source or observation history. Affiliation verification and a formal dispute flow have not launched yet.
Snapshot received: 9 Aug 2026, 19:59 UTC.