
iDevice Wearables
io.github.ralphieusaPublished by GitHub account ralphieusav1.0.1Updated Oct 27, 2026
Wearable tech roadmaps: Apple, Meta, Samsung, Google, Oura. Claims, timelines, analysis.
The publisher's own server: iDevice Buyer's Guide
Overview
Remote MCP endpoint giving assistants access to wearable tech roadmaps and claims for Apple, Meta, Samsung, Google and Oura.
- What you can do
- Look up wearable tech roadmaps covering Apple, Meta, Samsung, Google and Oura.
- Review claims and timelines tied to those roadmap entries.
- Draw on analysis of the wearable market and product plans.
- When to use it
- Useful when you need background on upcoming or rumored wearable devices from major vendors, or want claims and timelines summarized for research, comparison or writing.
- Requirements
- A remote MCP endpoint at idevice.com over streamable HTTP; no local package. An API key sent in the X-API-Key header, obtained from the provider's site.
Installation
In SourceWeft
- Open iDevice Wearables in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ralphieusa%2Fidevice-wearables/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"idevice-wearables": {
"type": "http",
"url": "https://idevice.com/api/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
